Skip to content
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

Could you please think about offering a CaseInsensitiveNamingConvention? #781

Open
schittli opened this issue Feb 20, 2023 · 0 comments
Open

Comments

@schittli
Copy link

Hello

thank you very much for sharing your great work!
I use YamDotNet for non-profit projects and it's great to have your library.

Is your feature request related to a problem? Please describe.

Our technically quite skilled users can edit the yaml files directly.
By far the most common mistakes they make are in the capitalization of property names.
Therefore, they either need support to fix the issue or we have to program the application fault-tolerant.
But because the property names are 99% correct and only the case is wrong, there is a much more elegant solution…

Describe the solution you'd like

It would be very helpful if you could provide this INamingConvention provider: CaseInsensitiveNamingConvention
This would allow us to easily make YamlDotNet more fault tolerant 😊

Describe alternatives you've considered

Of course, any application you could somehow handle these errors itself.

But if the application is allowed to be fault tolerant with the configuration files,
then something like a CaseInsensitiveNamingConvention would be a very elegant solution.

Thanks a lot, kind regards,
Thomas

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

No branches or pull requests

2 participants