When using ConfigSchemaGenerator, the casing of segments in the config path should be ignored. This is because configuration keys in .NET are case-insensitive.
For example, the following entries should be merged into a single subtree:
The same problem possibly applies to the class properties.
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version info
No response
Anything else?
This should be easy to fix, because JsonObject has a constructor that takes a JsonNodeOptions, which contains the boolean property PropertyNameCaseInsensitive.
Is there an existing issue for this?
Describe the bug
When using ConfigSchemaGenerator, the casing of segments in the config path should be ignored. This is because configuration keys in .NET are case-insensitive.
For example, the following entries should be merged into a single subtree:
I would expect the difference in casing to be ignored, so that the JSON fragment below is produced:
The actual behavior is that no unification takes place:
The same problem possibly applies to the class properties.
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version info
No response
Anything else?
This should be easy to fix, because
JsonObject
has a constructor that takes aJsonNodeOptions
, which contains the boolean propertyPropertyNameCaseInsensitive
.