You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. create a JSON string containing extra attributes
2. invoke Gson.fromJson supplying a class with fewer elements
3. GSON successfully instantiates the class without protesting about the
existence of extra attributes in the string.
What is the expected output? What do you see instead?
1. define class A containing two fields: name and surname
2. define class B containing only one field: name
3. transform an instance of class A to Json string and use the Json string
to create an instance of class B.
GSON doesn't complain. Even if this is the intended behavior, shouldn't
there be an option to enforce stricter parsing?
What version of the product are you using? On what operating system?
gson-1.4
Please provide any additional information below.
Original issue reported on code.google.com by [email protected] on 22 Jan 2010 at 10:13
I think a reasonable fix for this would be to permit the user to register a
handler to be notified whenever an unknown property is encountered. Perhaps
this:
interface UnknownFieldHandler {
void handle(JsonObject object, String name, JsonElement value);
}
Then we could build in a few implementations: one that ignores unknown fields,
one that logs unknown fields, and one that throws on unknown fields. Users
could configure their GSON to be as strict or forgiving as necessary.
Original comment by limpbizkit on 3 Nov 2010 at 4:53
Changed title: Support handlers for unknown properties, useful for error handling
Original issue reported on code.google.com by
[email protected]
on 22 Jan 2010 at 10:13Attachments:
The text was updated successfully, but these errors were encountered: