Add workaround to fix decoding of nested structs #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Poison has a bug when using Poison.decode!/2 with automatic conversion to structs that causes the Poison.Decoder protocol for the corresponding struct to be called twice. What ends up happening with the DocuSign models is that the second decode (using default values for the struct) overwrites the ones coming for the response. This workaround avoids calling the Poison.Decoder protocol a second time. For more information see: devinus/poison#191
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Poison has a bug when using
Poison.decode!/2with automatic conversion to structs that causes thePoison.Decoderprotocol for the corresponding struct to be called twice. What ends up happening with the DocuSign models is that the second decode (using default values for the struct) overwrites the ones coming for the response.This workaround avoids calling the
Poison.Decoderprotocol a second time.For more information see: devinus/poison#191