Draft: Demo permissive serialization model for Go SDK #48
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 PR demonstrates the different serialization options outlined in this document:
https://www.notion.so/buildwithfern/Golang-Permissive-Deserialization-232b23082e4c80d0b47bd288fb28fd5d
With some simple test cases for demonstrating failure modes and expected outputs of each option. At the time of writing invalid deserialization is only demonstrated by the
GetPayoutResponse.Payout.ID
fieldAdditionally, it looks like the existing
internal.ExtractExtraProperties
performs an unnecessary secondary unmarshal in theUnmarshalJSON
call path (1, 2). The PR also includes an additionalinternal.ExtractExtraPropertiesUnmarshalled
function to reuse the first unmarshalled object for comparing keys agains the extra properties map