We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Spring Data REST might be useful to address #95 , #94 without the need to write lots of custom code for pagination and sorting.
Spring Data REST generates API endpoints automatically with consistent sorting and pagination by default.
Spring Data REST generates a Hypermedia REST API which is not what we want or need for GLVD, we rather want 'JSON over HTTP' which can't be meaningfully built with Spring Data REST.
Without Spring Data REST pagination and sorting has to be implemented manually.
Result of the evaluation: Don't use Spring Data REST for glvd.
The text was updated successfully, but these errors were encountered:
thank you for the detailed research and thinking it through!
✅ Don't use Spring Data REST for glvd.
Sorry, something went wrong.
No branches or pull requests
Spring Data REST might be useful to address #95 , #94 without the need to write lots of custom code for pagination and sorting.
Spring Data REST generates API endpoints automatically with consistent sorting and pagination by default.
Spring Data REST generates a Hypermedia REST API which is not what we want or need for GLVD, we rather want 'JSON over HTTP' which can't be meaningfully built with Spring Data REST.
Without Spring Data REST pagination and sorting has to be implemented manually.
Result of the evaluation:
Don't use Spring Data REST for glvd.
The text was updated successfully, but these errors were encountered: