Split api into version namespace #41
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
For future-proofing, it's always a good idea to put the API in its own version namespace. This way, if we ever want to replace the API with something different, we can just add a new version.
We should research the different ways to implement this system. The most straightforward approach would be to just use a
/v1/
prefix for all URLs, but this does break the RESTful rule of each resource having a unique identifier. This page provides more info about the various approaches we could try.