-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Question: how to apply deserialize_struct_case_insensitive to a struct? #7
Comments
Hi @jlgerber ! Yes, the name is, unfortunately, confusing, I had plans to reorganise everything differently, but it is still yet to happen. And your thoughts are absolutely logical and correct and I apologise for having named it that way. I'll see, perhaps, it is possible to rewrite it so that it can indeed be applied to a struct. |
Thank you for the prompt reply. Fortunately, I realized that i only really had to support keys with first letters capitalized so i used aliases. |
You have still made a reasonable point. As I have wanted for so long to fix this, I now have another good reason for that. So, I'll close it and let you know once I do that. Thank you for reaching out and contributing! |
@vityafx - do you have any updates? It seems to me that I'm not sure how this would be possible to apply this to the parent struct EDIT: arguably, using |
I agree with the What kind of an update were you looking for? Just renaming/reorganisation of the crate's content or, perhaps, anything else? |
You had written before:
And I was hopeful, that maybe you had found a way to avoid using a nested struct. Or maybe your comment applied to clarifying the usage? |
Yes, so unfortunately it was more, if not only, clarifying the situation and the absence of a good workaround. |
I am a bit confused by deserialize_struct_case_insensitive. It is categorized as a container_attribute in serde-aux's docs. However, the example seems to show it used as a field attribute. If it is a container_attribute, should I be able to do something like this?
The text was updated successfully, but these errors were encountered: