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
{{ message }}
This repository was archived by the owner on Nov 15, 2018. It is now read-only.
The current code handles all (dynamic(example: ExpandoObject implements IDictionary<string,object>) or not) dictionaries which implement IDictionary<string, object> in a case Insensitive way. This is an incorrect behavior.
For example:
When Json.net deserializes data into a regular IDictionary<,> it considers the keys case-sensitive.
When Json.net deserializes data into a regular Poco type, it considers the property names case-Insensitive.
Considering the above behavior, we should do the following in json patch:
For dynamic types (like ExpandoObject, DynamicObject etc.), the matching of keys should be case-Insensitive. This is to keep the behavior consistent with a Poco type where the property names are considered case-Insensitive.
For dictionaries, keep the default json.net behavior, i.e. keep them case sensitive.
The current code handles all (dynamic(example: ExpandoObject implements
IDictionary<string,object>
) or not) dictionaries which implementIDictionary<string, object>
in a case Insensitive way. This is an incorrect behavior.For example:
Considering the above behavior, we should do the following in json patch:
@dougbu @rynowak
The text was updated successfully, but these errors were encountered: