This repository was archived by the owner on May 11, 2018. It is now read-only.
Deep serialization of nested-resource(s)#18
Open
hontas wants to merge 4 commits into
Open
Conversation
If a resource contains one or a list of resources they will be serialized to. This gives greater control of the JSON data representation. Also made resourceName optional as a nested resource would otherwise mess up the structure.
Now using Ember.isArray and Ember.Object.detectInstance
Another try, now providing a nested variable to determin if a resource is nested and should be returned without being wrapped in a named object even though it might have resourceName-property.
Author
|
Got a little confused cause we don't use resourceName in our implementation. Sorry 'bout that. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
If a resource contains other resources they will be serialized to. This gives greater control of the JSON data representation.
Nested resource should not contain resourceName as that will mess up the structure.