Johannes/gson-comments
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
cc5cbe5a1f
gson-comments/gson/GSON 2.0 NOTES.txt

69 lines
3.7 KiB
Plaintext
Raw Normal View History

Retire two old bad features - overriding primitive type adapters - auto unwrapping of single element arrays
2011-09-09 06:20:25 +02:00
What's new in GSON 2.0
GSON 1.x used to automatically unwrap single-element arrays as necessary.
GSON 2.x doesn't.
com.google.gson.functional.ArrayTest.testSingleStringArrayDeserialization
Throw the right exceptions when primitives fail to parse.
2011-09-09 07:04:24 +02:00
com.google.gson.functional.PrimitiveTest#testPrimitiveIntegerAutoboxedInASingleElementArrayDeserialization
com.google.gson.functional.PrimitiveTest#testPrimitiveLongAutoboxedInASingleElementArrayDeserialization
com.google.gson.functional.PrimitiveTest#testPrimitiveBooleanAutoboxedDeserialization
com.google.gson.functional.PrimitiveTest.testPrimitiveBooleanAutoboxedInASingleElementArrayDeserialization
com.google.gson.functional.PrimitiveTest.testPrimitiveDoubleAutoboxedInASingleElementArrayDeserialization
com.google.gson.functional.PrimitiveTest.testBigDecimalInASingleElementArrayDeserialization
com.google.gson.functional.PrimitiveTest.testBigIntegerInASingleElementArrayDeserialization
Don't unwrap single-element String arrays
2011-09-09 07:41:35 +02:00
com.google.gson.functional.StringTest.testStringValueAsSingleElementArrayDeserialization
Converted EnumTypeAdapter to new style. Got rid of default Hierarchy Serializer/Deserializers from DefaultTypeAdapters. Got rid of methods for gettting default serializers/deserializers/instance creators. Instead we reuse the static final instances. Fixed warnings in TypeAdapters where a parameterized type T was hiding the parameterized T in methods. Removed support to unwrap single element array of enums into enum values. Also removed the test that verifies this behavior.
2011-09-16 07:40:05 +02:00
com.google.gson.functional.EnumTest.testTopLevelEnumInASingleElementArrayDeserialization
Retire two old bad features - overriding primitive type adapters - auto unwrapping of single element arrays
2011-09-09 06:20:25 +02:00
GSON 1.x permitted primitive types to be overridden
GSON 2.x doesn't.
Throw the right exceptions when primitives fail to parse.
2011-09-09 07:04:24 +02:00
com.google.gson.functional.ArrayTest.testArrayOfPrimitivesWithCustomTypeAdapter
com.google.gson.functional.PrimitiveTest.testOverridingDefaultPrimitiveSerialization
GSON 1.x rejects integers that have any fraction, even if it is ".0"
GSON 2.x permits integers to have ".0" fractions like "1.0"
Don't support oversized values like 30-character integers
2011-09-09 07:11:59 +02:00
com.google.gson.functional.PrimitiveTest.testDeserializingDecimalPointValuesAsIntegerFails
GSON 1.x truncates oversized large integers and longs
GSON 2.x fails on oversized large integers and longs
com.google.gson.functional.PrimitiveTest.testDeserializingBigIntegerAsInteger
GSON 1.x uses arbitrary precision for primitive type conversion (so -122.08e-2132 != 0) GSON 2.x uses double precision (so -122.08e-2132 == 0)
2011-09-09 07:23:01 +02:00
com.google.gson.functional.PrimitiveTest.testDeserializingBigIntegerAsLong
GSON 1.x uses arbitrary precision for primitive type conversion (so -122.08e-2132 != 0)
GSON 2.x uses double precision (so -122.08e-2132 == 0)
Forbid custom serializers for primitive types (so we can avoid boxing in the reflective and array adapters)
2011-09-09 08:26:21 +02:00
com.google.gson.functional.PrimitiveTest.testDeserializingBigDecimalAsLongFails
GSON 1.x supports type adapters for primitive types
GSON 2.x doesn't
com.google.gson.functional.CustomTypeAdaptersTest.testCustomSerializerForLong
com.google.gson.functional.CustomTypeAdaptersTest.testCustomDeserializerForLong
Let the runtime throw on circular references
2011-09-28 21:38:43 +02:00
GSON 1.x throws IllegalStateException on circular references
GSON 2.x lets the runtime throw a StackOverflowError
com.google.gson.functional.CircularReferenceTest.testCircularSerialization
com.google.gson.functional.CircularReferenceTest.testSelfReferenceSerialization
com.google.gson.functional.CircularReferenceTest.testSelfReferenceArrayFieldSerialization
Use the same behavior in all situations when an InstanceCreator returns a subclass. Previously we would set the field if the created instance is being assigned to a field of another object. We wouldn't set it when the created instance is a collection element or the top-level object.
2011-09-29 18:38:24 +02:00
com.google.gson.functional.CircularReferenceTest.testSelfReferenceCustomHandlerSerialization
GSON 1.x sometimes sets subclass fields when an InstanceCreator returns a subclass.
This occurs only when the value is a field of another object: not when its
the top level object or a collection element.
GSON 2.x sets fields of the requested type only
com.google.gson.functional.InstanceCreatorTest.testInstanceCreatorReturnsSubTypeForField
Fixed com.google.gson.functional.VersioningTest.testIgnoreLaterVersionClassDeserialization by changing Gson behavior incompatibly (but more consistent). GSON 1.x applies different rules for versioning for classes vs fields. So, if you deserialize a JSON into a field that is supposed to be skipped, the field is set to null (or default value). However, if you deserialize it to a top-level class, a default instance is returned. GSON 2.x returns null for the top-level class.
2011-09-30 00:15:37 +02:00
Adopt JsonElementWriter in GSON. Add setSerializeNulls() to JsonWriter, so nulls can be skipped from serialization. This does not yet impact JsonElementWriter. One change in behavior: if the only value is skipped, we now emit "null" rather than "".
2011-09-30 09:08:44 +02:00
Fixed com.google.gson.functional.VersioningTest.testIgnoreLaterVersionClassDeserialization by changing Gson behavior incompatibly (but more consistent). GSON 1.x applies different rules for versioning for classes vs fields. So, if you deserialize a JSON into a field that is supposed to be skipped, the field is set to null (or default value). However, if you deserialize it to a top-level class, a default instance is returned. GSON 2.x returns null for the top-level class.
2011-09-30 00:15:37 +02:00
GSON 1.x applies different rules for versioning for classes vs fields. So, if you deserialize a
Adopt JsonElementWriter in GSON. Add setSerializeNulls() to JsonWriter, so nulls can be skipped from serialization. This does not yet impact JsonElementWriter. One change in behavior: if the only value is skipped, we now emit "null" rather than "".
2011-09-30 09:08:44 +02:00
JSON into a field that is supposed to be skipped, the field is set to null (or default value).
Fixed com.google.gson.functional.VersioningTest.testIgnoreLaterVersionClassDeserialization by changing Gson behavior incompatibly (but more consistent). GSON 1.x applies different rules for versioning for classes vs fields. So, if you deserialize a JSON into a field that is supposed to be skipped, the field is set to null (or default value). However, if you deserialize it to a top-level class, a default instance is returned. GSON 2.x returns null for the top-level class.
2011-09-30 00:15:37 +02:00
However, if you deserialize it to a top-level class, a default instance is returned.
Adopt JsonElementWriter in GSON. Add setSerializeNulls() to JsonWriter, so nulls can be skipped from serialization. This does not yet impact JsonElementWriter. One change in behavior: if the only value is skipped, we now emit "null" rather than "".
2011-09-30 09:08:44 +02:00
GSON 2.x returns null for the top-level class.
com.google.gson.functional.VersioningTest.testIgnoreLaterVersionClassDeserialization
GSON 1.x creates the empty string "" if the only element is skipped
GSON 2.x writes "null" if the only element is skipped
com.google.gson.functional.ObjectTest.testAnonymousLocalClassesSerialization
com.google.gson.functional.FieldExclusionTest.testInnerClassExclusion
com.google.gson.functional.VersioningTest.testIgnoreLaterVersionClassSerialization
Reference in New Issue Copy Permalink