You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support finding property names via match so that a case insensitive regex may be used or support using JsonPath and match property names using case insensitive match. Alternative would be to provide a way to add custom/extendable ISelector implementations and inject them into the framework.
Describe alternatives you've considered.
I have considered taking the full json payload and doing a ToLower() on the whole but then the content/values are lower case.
Is there any other information you'd like to share regarding this enhancement?
I understand that this would have a larger performance impact because the JsonObject.TryGetPropertyValue does not support a case insensitive match and would instead require iteration over the property names of the object to find the match and then use that to get the value. This is why I would expect it to be an "opt-in" approach if you want to do a case insensitive and leave the default to doing the current functionality.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Alternative would be to provide a way to add custom/extendable ISelector implementations and inject them into the framework.
The spec's only extension point right now is expression functions. I'm not open to offering a major feature like this as it's very much related to the spec framework itself, and I want to remain as close to spec as possible.
Again, the best way to effect change is by making proposals to the spec.
Nuget Package
JsonPath.Net
Package Version
1.0.0
Can this library make doing something simpler?
Support finding property names via match so that a case insensitive regex may be used or support using JsonPath and match property names using case insensitive match. Alternative would be to provide a way to add custom/extendable ISelector implementations and inject them into the framework.
Describe alternatives you've considered.
I have considered taking the full json payload and doing a ToLower() on the whole but then the content/values are lower case.
Is there any other information you'd like to share regarding this enhancement?
I understand that this would have a larger performance impact because the JsonObject.TryGetPropertyValue does not support a case insensitive match and would instead require iteration over the property names of the object to find the match and then use that to get the value. This is why I would expect it to be an "opt-in" approach if you want to do a case insensitive and leave the default to doing the current functionality.
Code of Conduct
The text was updated successfully, but these errors were encountered: