Json: How to handle not existing member

Currently, I am trying to implement a maybe weird case in my internal project. The basic concept is that any JSON object can be part of a JSON array.

So something like that:

[
   {
      "animal": "cat"
   },
   {
      "color": "green"
   }
]

If I now try to run something like that:

JsonDocument data = null; // something sets the value of JsonDocument so it's not null
data.Any(config: System.Linq.Dynamic.Core.SystemTextJson.Config.SystemTextJsonParsingConfig.Default, "x => x.number == 5"));

I will now get an exception like that:

The binary operator Equal is not defined for the types 'System.Object' and 'System.Int32'.

My question is, is there some kind of expression that I can write, that makes it possible to make a member optional?

Or some setting that I can set?

@paule96

@paule96
Maybe you can try this:
https://dynamic-linq.net/advanced-configuration#allowequalsandtostringmethodsonobject-since-v1.6.0

add test cases for not exsisting members in where clause (zzzprojects…

@StefH

@StefH
We tried this but it doesn't help us.
But I created reproduction tests with the commit:

paule96@c0b8e02

The following tests are falling:

compare a non exsisting value with a number value (notExisting > 1)
compare a non exsisting value with a boolean value (notExisting == true)

Comparing to strings are just working

@paule96

@paule96
OK, thanks for the unit tests.

However, I would expect that when you try to query an non-existing member, you would get error like:
Unhandled exception. Microsoft.CSharp.RuntimeBinder.RuntimeBinderException: 'xxx' does not contain a definition for 'number'

Yes I would expect the same for the default path.
But also when you work with json, it's kinda normal to miss members.

So it would be nice to have a syntax or a configuration that allows to compare to non existing members.

#954

I did fix the code so that your unit tests pass. However you will need to provide ConvertObjectToSupportComparison = true and missing members are not yet supported.

very cool thank you. We will try it out the next days

I will probably create new version this weekend

@StefH

@StefH we found one scenario that may produce invalid results. But it's a bit hard to decide because we are in a world between JSON and C#.

x.notExsting == false

This currently returns true. But actually, because in JS/JSON world x.notExsting is undefined and not false, it should return false.

What if you compare with a nullable bool with value false?

How do you mean? From a plain C# view like that:

bool? test = null;
var result = test == false;
Console.WriteLine("Hello " + result);

The result would be Hello false.

@StefH

@StefH ping :)

I will take a look this weekend.

Probably I will add a bool config setting with default to true to normalize the json.

This PR should solve this:
#958

Very cool. Will try ut next week

Navigation Menu

Repository navigation

Json: How to handle not existing member #952

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Json: How to handle not existing member #952

Description

Activity

StefH commented on Oct 25, 2025

paule96 commented on Oct 30, 2025

StefH commented on Nov 1, 2025

paule96 commented on Nov 1, 2025

StefH commented on Nov 2, 2025

StefH commented on Nov 2, 2025

paule96 commented on Nov 3, 2025

StefH commented on Nov 5, 2025

paule96 commented on Nov 10, 2025

StefH commented on Nov 10, 2025

paule96 commented on Nov 10, 2025

paule96 commented on Nov 13, 2025

StefH commented on Nov 14, 2025

StefH commented on Nov 15, 2025

paule96 commented on Nov 15, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions