Conversation
Adds serialization options to be used in generating resource level meta and resource level links through procs.
Contributor
There was a problem hiding this comment.
How about:
Meta information can be included for each resource using the
metamethod in the resource declaration. For example:
Contributor
Author
|
Closing in favor of another approach. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds resource meta support.
Adds serialization options to be used in generating resource level meta and resource level links through procs.
Comments on the
custom_generation_optionsmethod in the serializer would appreciated. I'm thinking this will also be used in the generation of custom links (see #486). As it's just a hash we should be able to easily change it, but I'd like to get it right to start.