-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decode to maps #24
Comments
Support for nested maps, at least, should definitely be included—since we can already support arrays with |
I agree this would be a good feature. Unfortunately I don't have time to work on this at the moment, marking as HelpWanted. |
This issue has been automatically marked as stale because it hasn't seen a recent update. It'll be automatically closed in a few days. |
Any progress? |
This issue has been automatically marked as stale because it hasn't seen a recent update. It'll be automatically closed in a few days. |
have you to resolve this ? |
If you know your fields (and their types) only at runtime, there is no way to decode values to them. Structs have to be defined at compile time.
A possible solution would be to support maps as target values. For example:
There could also be support for nested maps, but I guess it would be ok to just support flat maps with fields like "nested.key".
Other ideas?
The text was updated successfully, but these errors were encountered: