-
Notifications
You must be signed in to change notification settings - Fork 808
Support for a YAML configuration provider #1904
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
Comments
If I'm not wrong this issue is already logged from 1.0, but it closed, coz there's no plan to support it |
Thanks for the update @hishamco but 1.0 is a long time ago, time to see if we can revise that decision! |
Why should it be in the box? |
Because YAML is used more and more + .NET is always mentioned to be a good candidate for microservices. However, microservices are often shipped via containers wherein the container space YAML is used for configuration over JSON. |
We're not going to change the default from JSON to Yaml, I'd suggest using the above library if you want yaml based configuration files. |
I'm not saying that it should be the new default, I'm just wondering why YAML is not supported OOTB. Anyhow, I could only ask. |
Several reasons:
|
A pity but fair enough |
In container land, YAML is used in favor of JSON which is not supported in .NET Core OOTB. Would be good to have a YAML configuration provider.
This is already available via https://github.com/andrewlock/NetEscapades.Configuration but would be good to have official support for this OOTB.
The text was updated successfully, but these errors were encountered: