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
The definition of REST contains many mandatory constraints described here: https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm REST APIs are hypertext driven https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven while your API is not. I understand the confusion, because people learned REST from stackoverflow and from tutorials have only a vague and false idea of what REST is. Learning how it should work is hard, implementing it is even a lot harder. What we really have here is just some sort of CRUD API. https://www.bmc.com/blogs/rest-vs-crud-whats-the-difference/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The definition of REST contains many mandatory constraints described here: https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
REST APIs are hypertext driven https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven while your API is not. I understand the confusion, because people learned REST from stackoverflow and from tutorials have only a vague and false idea of what REST is. Learning how it should work is hard, implementing it is even a lot harder. What we really have here is just some sort of CRUD API. https://www.bmc.com/blogs/rest-vs-crud-whats-the-difference/
The text was updated successfully, but these errors were encountered: