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

Stack Overflow #488

Closed
GoogleCodeExporter opened this issue Mar 19, 2015 · 4 comments
Closed

Stack Overflow #488

GoogleCodeExporter opened this issue Mar 19, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Run the attached test

What is the expected output? What do you see instead?
A JSON document


What version of the product are you using? On what operating system?
gson-2.2.2 under Eclipse Indigo SR2 under Windows 7.


Please provide any additional information below.

Original issue reported on code.google.com by thomh...@gmail.com on 20 Nov 2012 at 4:51

Attachments:

@GoogleCodeExporter
Copy link
Author

Please isolate bugs when reporting them.

Original comment by limpbizkit on 21 Nov 2012 at 12:31

  • Changed state: Invalid

@GoogleCodeExporter
Copy link
Author

It would be nice if GSON detected circular dependencies.
Or gave some way to limit depth to, say, 2 levels.

Original comment by dynaw...@gmail.com on 23 Jan 2013 at 4:03

@GoogleCodeExporter
Copy link
Author

Or gave some means to limit which values are being serialized. such as to 
exclude something you know is a circular reference. Probably a piece of data 
that doesn't explain the data you are looking at anyway.

Original comment by Boneless1213@gmail.com on 26 Feb 2013 at 7:23

@GoogleCodeExporter
Copy link
Author

Do you know what field(s) are causing the circular reference? If so, we can use 
an ExclusionStrategy and the .shouldSkipField() method to handle it.
The problem is, I can't figure out what part of the exception is causing the 
circular reference.

Original comment by bradyvid...@gmail.com on 4 Mar 2014 at 8:17

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

No branches or pull requests

1 participant