Add rmpv::ext::to_value_named to keep struct keys #337
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.
The current
rmpv::ext::to_value
implementation turns Structs intoValue::Array<Value::String>
which is not deserializable by other languages.Technically I would call this a bug and opt to change the existing
to_value
implementation, but to stay cautious of not breaking existing users' code I think it makes sense to introduce a newto_value_named
fn which instead turns Structs intoValue::Map
and maintains their keys.Fixes #190