Fixes #42643 allow keys with colons in JSON config#66886
Fixes #42643 allow keys with colons in JSON config#66886SteveDunn wants to merge 17 commits intodotnet:mainfrom
Conversation
…oded jsonfileprovider to backtick which'll probably break lots of tests
|
Tagging subscribers to this area: @dotnet/area-extensions-configuration Issue DetailsNote: hardcoded, for now,
|
… Need the provider to specify their delimiter (to do next)
Now need to remove previous effort of passing separators everywhere
…that each provider can have a separate key
...aries/Microsoft.Extensions.Configuration.Json/ref/Microsoft.Extensions.Configuration.Json.cs
Outdated
Show resolved
Hide resolved
|
see #42643 (comment) for using array instead of direct keys you might get more flexible code for the original need |
src/libraries/Microsoft.Extensions.Configuration.Binder/src/ConfigurationBinder.cs
Outdated
Show resolved
Hide resolved
...aries/Microsoft.Extensions.Configuration.Json/ref/Microsoft.Extensions.Configuration.Json.cs
Outdated
Show resolved
Hide resolved
src/libraries/Microsoft.Extensions.Configuration.Json/tests/JsonConfigurationTest.cs
Outdated
Show resolved
Hide resolved
...libraries/Microsoft.Extensions.Configuration.FileExtensions/src/FileConfigurationProvider.cs
Outdated
Show resolved
Hide resolved
...Extensions.Configuration.Abstractions/ref/Microsoft.Extensions.Configuration.Abstractions.cs
Show resolved
Hide resolved
I moved it from WIP as all it fixes the problem reported in the Issue. As you can see though, it did require some overloads to allow the user to specify their new separator string for the keys. I couldn't think of another way of allowing this, so I'm open to suggestions and ideas. |
... and, 6 days later I find the button that really does move it from draft! 🤦 |
|
Closed for now until the API Proposal is reviewed: |
Each provider has their own
Separatorfield (defaults to:). If users have colons in their keys, they can provide`(or similar) as the optional parameter to the various methods.Fixes #42643