Why custom IncludeTypeNameInDictionaryKeyFieldNameConvention/DictionaryConverter is needed?
It does allmost exatcly same things that EPiServer.Find.Json.IncludeTypeInNativeFieldNamesInterceptor/DictionaryConverter but in less intelligent way:
commerce dictionary converter fails to parse inner dictionaries like: "{"dictionary": { "key": {"innerKey" : "value"}}}" due to absence of following check (that is present if default dictionary converter):
if (reader.TokenType == JsonToken.Null)
{
return null;
}
if (existingValue == null)
{
existingValue = objectType.GetConstructor(new Type[0]).Invoke(new object[0]);
}
Why custom IncludeTypeNameInDictionaryKeyFieldNameConvention/DictionaryConverter is needed?
It does allmost exatcly same things that EPiServer.Find.Json.IncludeTypeInNativeFieldNamesInterceptor/DictionaryConverter but in less intelligent way:
commerce dictionary converter fails to parse inner dictionaries like: "{"dictionary": { "key": {"innerKey" : "value"}}}" due to absence of following check (that is present if default dictionary converter):