Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine best way to version API enpoints #9

Open
zmon opened this issue Jul 6, 2019 · 1 comment
Open

Determine best way to version API enpoints #9

zmon opened this issue Jul 6, 2019 · 1 comment

Comments

@zmon
Copy link
Member

zmon commented Jul 6, 2019

When the backend changes it's API we need an easy way to have different versions of the front end to use the correct version of the API.

For example pagination to the Applicant, the grid is being changed to pass back pagination information as well as data. The current version is only passing back data.

@zmon zmon added enhancement New feature or request requires backend change labels Jul 6, 2019
@mattsplat
Copy link
Collaborator

The approach I am seeing done is essentially having a separate set of routes and controllers for each version on the backend. For the frontend we can just keep the version on separate branches.

@zmon zmon added the SPA label Aug 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants