Possible fix for issue #7930 HotChocolate.Types.Filters Null Reference issue

[olu-lebara]

Changed order of operations during combine

• If filter condition is complex, expression for IQueryable could have mistakes. For example

• ($r.ItemSetting).Data == 123 && $r.ItemSetting != null

• first it checks property value, and only then checks object is not null.

• In my case (described in original topic) fix changed order and issue is gone

Closes #7930

Original post with details and issue explanation - #7850

[CLAassistant]

All committers have signed the CLA.

[michaelstaib]

@olu-lebara We are not doing any fixes to 11 ... can you create a pr to main?

[michaelstaib]

Types.Filters does no longer exist. HotChocolate.Data is the replacement.

[olu-lebara]

Thanks @michaelstaib, unfortunately issue is not reproduced (at least in my case) for HotChocolate.Data and last version of HotChocolate. Filters (where condition) was redesigned a lot, and has different filter conditions format. That's why we cannot update to latest version due to compatibility with old queries.
Is it possible somehow to use old filtering format (_some, _any) with HotChocolate.Data package?