Skip to content
This repository has been archived by the owner on May 11, 2018. It is now read-only.

Deep serialization of nested-resource(s) #18

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

hontas
Copy link

@hontas hontas commented May 16, 2013

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.

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.
@hontas
Copy link
Author

hontas commented May 16, 2013

Got a little confused cause we don't use resourceName in our implementation. Sorry 'bout that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant