Skip to content

wip: Strict deserialization returns error on any unknown xml field#194

Open
jggc wants to merge 1 commit intoluminvent:mainfrom
jggc:feat/strictDeserialization
Open

wip: Strict deserialization returns error on any unknown xml field#194
jggc wants to merge 1 commit intoluminvent:mainfrom
jggc:feat/strictDeserialization

Conversation

@jggc
Copy link

@jggc jggc commented Oct 14, 2024

This is a feature request with some sample code to support the idea.

I am creating a strict parser that will deserialize a rather large configuration file from a running environment, modify it and write it back.

I need to be 100% sure that I won't be modifying anything else and I want complete type safety so I decided to go with yaserde.

However, I tried setting #[yaserde(deny_unknown_fields)] but it does nothing (or I don't understand what it should be doing).

Question 1 : Is this an existing feature that I missed ?

Question 2 : Is this catch all case of the event name the right place to return Err(...) ?

If so, I may very well try to make a cleaner implementation based on deny_unknown_fields if that sounds correct to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant