Provide an @Required annotation to indicate that a field must be present
``` See discussion at http://groups.google.com/group/google- gson/browse_thread/thread/6cfdcc56742357da During deserialization, Gson should throw a JsonParseException if it finds that a field marked with @Required is not present. During serialization, Gson should always write out a field marked @Required even if it is null. ``` Original issue reported on code.google.com by `inder123` on 17 Oct 2008 at 10:31
Posted by GoogleCodeExporter on Mar 19, 2015, 6:22 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.7,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
Provide an @Required annotation to indicate that a field must be present
``` See discussion at http://groups.google.com/group/google- gson/browse_thread/thread/6cfdcc56742357da During deserialization, Gson should throw a JsonParseException if it finds that a field marked with @Required is not present. During serialization, Gson should always write out a field marked @Required even if it is null. ``` Original issue reported on code.google.com by `inder123` on 17 Oct 2008 at 10:31
Comments (0)
No comments yet. Start the discussion.