-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Json:api support? #110
Comments
Yes. You can return in response whatever you want, so there is practically no problem to implement whichever specification you would like. apitte/negotiation could help you with automated data transformation which will improve with implementation of #97 Also link generator is planned, see #94 I don't know what more can we do to support schemas like that, maybe you could present your implementation. |
Hmm looks interesting, will give a try. Do you know when link generator will be implemented in stable version? |
Not sure, it's a very complicated component. |
@mabar ok, negotiation transformer is working, but one issue to solve. How i could get routes? According to json:api, there have to be links to other entities. Is there some way? Or i need to wait for linkgenerator? |
Currently all endpoints with their full paths are available in Schema. https://github.com/apitte/core/blob/master/src/Schema/Schema.php We are using OpenApi (via apitte/openapi) to document our api, so never thinked about it |
Is there a way how to implement Json:Api ? https://jsonapi.org/
Right now i am using slim fw where i am able to generate own response content with jsonapi renderer
The text was updated successfully, but these errors were encountered: