Add support for nested explicit wrappers #140
Merged
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.
Sometimes you need to fully specify a wrapper type. This is most common for situations when you need a custom wrapper type, but that type is embedded inside an outer generic type (like a List) that needs its own wrapper. In this case, it's not enough to specify the outer wrapper (the List wrapper) or the inner wrapper (the custom wrapper) alone. You need the full composition.
The new
WrapperSerialize
andWrapperDeserialize
properties on the GenerateSerialize, GenerateDeserialize, and GenerateSerde attributes can be used for this.