Split api into version namespace #41

New issue

Open

opened 2021-09-24 11:50:38 +02:00 by Jef Roosens · 1 comment

Jef Roosens commented

2021-09-24 11:50:38 +02:00

Owner

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.

Jef Roosens added this to the 1.0 - First Release milestone 2021-09-24 11:50:38 +02:00

Jef Roosens added the

enhancement

Backend

labels 2021-09-24 11:50:38 +02:00

Jef Roosens commented

2021-09-24 11:52:45 +02:00

Author

Owner

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.

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](https://restfulapi.net/versioning/) provides more info about the various approaches we could try.

This repository is archived. You cannot comment on issues.