Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Processed unresolved components on deserialization. #4

Merged
merged 2 commits into from
Apr 15, 2014

Conversation

Sonal4J
Copy link
Contributor

@Sonal4J Sonal4J commented Mar 12, 2014

  1. The changes would allow to process unresolved references during deserialize. If the order of elements in JSON is not in the desired order still it will resolve references and insert records.
  2. If any Limit Exceptions like 'Too many fields describes: 101' and 'Too many child relationships describes: 101' comes user will be able report it.

The changes would allow to process unresolved references during deserialize. If the order of elements in JSON is not in the desired order still it will resolve references and insert records.
Test methods added to process Unordered Records in JSON during deserialize and to catch Limit Exceptions like 'Too many fields describes: 101' and 'Too many child relationships describes: 101'.
afawcett added a commit that referenced this pull request Apr 15, 2014
Processed unresolved components on deserialization.
@afawcett afawcett merged commit 64df4e7 into afawcett:master Apr 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants