-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Hypermedia media types #291
Comments
I love this part, |
First of all I would like to see support for |
👍 This would be awesome! Just discovered Apiary and loving it so far, but would love to have the JSON API support. Is there any progress on this? Would love to help out. |
Hey @jamesdixon it is currently number 8 on the roadmap so no real progress just yet. I guess next step is to start carving out the RFC for the specification. If you want to play with that and draft a syntax for capturing actions-affordances that would work together with the current actions that would be sweet |
Thanks, @zdne. I'll see what I can do as I start working with Apiary a bit more -- definitely need more time to familiarize myself with how things work. Cheers. |
Using the information from the Attributes section and the Action section
The API Blueprint parser should be able to render Hypermedia media types on behalf of the user.
For example given following (pseudo) blueprint:
The response message payload body could be generated as:
Note this feature can be dramatically improved by implementing the #288 and #290 where the
- Affordances
could refer to a state (and therefore its collection of affordances):The text was updated successfully, but these errors were encountered: