Support resource identifier metadata #9
Conversation
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 basic support for metadata on resource identifiers, as described in the spec:
Our project uses that meta information to convey preferred sort order on a relation. The server does not guarantee preserved array ordering, so we need to use that metadata.
I'm aware the API for this is not optimal; I'll have to access
<collection>.linkageand then map its metadata to each resource by myself. API-wise I would prefer having aResourceIdentifier.resourceaccessor for convenience, but I believe it would lead to a lot of work for a comparatively small gain.All tests are passing, and I have manually run this against our production back-end to verify that I can access the metadata as described.