[RFR] Clarify Map logic, allow nested fields#549
Merged
jeromemacias merged 19 commits intomasterfrom Jul 10, 2015
Merged
Conversation
Member
Author
|
Switching to RFR! |
package.json
Outdated
Contributor
There was a problem hiding this comment.
admin-config 0.2.5 version had been published.
Member
Author
There was a problem hiding this comment.
Switched dependency to fixed version
jeromemacias
added a commit
that referenced
this pull request
Jul 10, 2015
[RFR] Clarify Map logic, allow nested fields
This was referenced Jul 13, 2015
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
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.
Currently, callbacks registered on fields with
map()are applied to the REST response to turn it into an Entry (when fetching results) AND to the entries to turn them into a response (when pushing modifications). It doesn't make sense, and prevents some new features, such as deeply nested fields (refs. #525).This PR fixes that. Now you can do things like:
to map REST responses looking like:
[ { "title": "War and Peace", "author": { "name": "Leo Tolstoi" } }, { "title": "Anna Karenina", "author": { "name": "Leo Tolstoi" } } ]Depends on marmelab/admin-config#20