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

Ensure that all API endpoints conform to HATEOAS #90

Open
devraj opened this issue Dec 3, 2023 · 0 comments
Open

Ensure that all API endpoints conform to HATEOAS #90

devraj opened this issue Dec 3, 2023 · 0 comments
Assignees

Comments

@devraj
Copy link
Member

devraj commented Dec 3, 2023

Is your feature request related to a problem? Please describe.
Hypermedia as the engine of application state (HATEOAS) is a constraint of the REST application architecture that distinguishes it from other network application architectures.

With HATEOAS, a client interacts with a network application whose application servers provide information dynamically through hypermedia. A REST client needs little to no prior knowledge about how to interact with an application or server beyond a generic understanding of hypermedia.

Our APIs should be HATEOAS compatible.

Describe the solution you'd like
I initially got reminded of this when I came across FastUI by @samuelcolvin which builds upon FastAPI, there are discussions on FastAPI about this, follow this discussion.

If you are wanting to understand the basic problem, then please read this essay

The task here is to provide a design pattern for APIs to implement when using this template.

Describe alternatives you've considered
NA

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant