-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Support for hierarchical keys? #76
Comments
We could think about an alternative solution for this. Feel free to open a PR if you want |
It's possible to either rollback to using the configuration approach, or to replicate the same funcionality for the structured data using the current json parser. What was the motivation for using System.Text.Json instead? |
This was the plan, there're new APIs that make parsing JSON much easier and more efficient |
Sorry @stepanStanc for this taking so long, please remind me is the hierarchical keys used colon in the past, I need to bring this feature back if it's necessary or think about alternative way |
Hierarchical keys are back 🚀, please let me know if you have any feedback |
In version 3.0.1 it was possible to use hierarchical keys (:) thanks to the configurations API that is used https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-7.0#configuration-keys-and-values. After this issue #29 and this change ecf7169 that stopped being supported in version 3.1.0.
Would it be possible to bring support for this back, or should an alternate approach be taken?
The text was updated successfully, but these errors were encountered: