Add (de-)serialization support for Iterable #1709
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds only support for (de-)serializing
Iterable
, but not any of its subtypes since it would not be possible to properly deserialize them again (see also #1708 and #1389).The targeted use case is classes with
Iterable
fields:However, since it only supports
Iterable
(and no subtypes) it might not be useful enough. It would be good to gather some feedback on how useful it would be and which use cases it would suit.Note that these changes might have an effect for serialization of fields with compile-time type
Iterable
for which previously the reflective adapter for the runtime type was used (see howTypeAdapterRuntimeTypeWrapper
chooses the type adapter).