Support decoding structs into Go maps #79
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.
As has been mentioned in #77, in some cases an XML-RPC struct member names are not known at compile time. This makes definitions of response datatypes much more complicated or not always possible.
To workaround this,
StrDecoder
can now acceptmap[string]any
values alongsidestruct
values.In order to not over-complicate things a limitation on the map's key type to be a
string
has been added.This new functionality should be backwards compatible as existing codebases could never use
map
datatypes for decoding, thus introducing additional flexibility to struct decoding won't cause any problems.Fixes #77