elgonzo

Just an addendum (and not strictly necessary). It just occured to me that the _ListItemsProvider_'s _GetValue_ method doesn't really need the concrete list type, because it could just create a...

@JamesNK > Doesn't your sample set MaxDepth to int.MaxValue? I am not the author of this issue report, but looking at the code in the opening post, it apparently does....

Note that floating point numbers in json **must** use the decimal dot. Decimal commas are not allowed by the json standard (https://www.json.org/json-en.html; as this would conflict with the comma separator...

@jflaga that's a different issue from the original issue report you posted under. According to their report, the OP **seems to want** decimal comma in json, which is not really...

Any feature-rich reflection-based serializer or library (like Newtonsoft.Json/Json.NET) is a struggle regarding trimming. As the documentation you linked to states: > Sometimes the existing design of an API will render...

Are you by any chance trimming when building in Release mode?

Then i would strongly recommend - if feasible - switching from Newtonsoft.Json to System.Text.Json, although i can't predict the success chance due to being oblivious of your project. Reflection-based serializers...

Well, it is caused -- or at least triggered -- by that mysterious type `MyList` that i and others don't know anything about. Proof of your example working when replacing...

@StefH > I tried to reproduce your issue with this unit test, but I could not reproduce it. That is because the left-hand side of the query (the `firstName` identifier)...

@StefH > Another part of the issue is this code: > ```var dynamicClass = (DynamicClass) Activator.CreateInstance(type);``` > Because the result from CreateInstance (which is actually another type : f__AnonymousType0`1[System.String]), the...