Tassilo Singhammer

It seems that a foreach loop in the test code is causing the issue. This code succeeds on Azure: ``` record Test(string Name); [Fact] public void Test_Bug_460395_oa136372() { List testItems...

Stack trace: ``` Failed Mapping.Tests.Test.MapperTest.Test_Bug_460395_oa136372 [183 ms] Error Message: Snapshooter.Exceptions.SnapshotTestException : The snapshot full name could not be evaluated. This error can occur, if you use the snapshot match within...

I get that via the OpenApi specification nullable fields can be declared by `nullable: true`. What seems to be a bit inconsistent to me is that if a field is...

Here is a demo project to reproduce the issue: [https://github.com/ChilliCream/hotchocolate/tree/tsi/empty-record-as-input](https://github.com/ChilliCream/hotchocolate/tree/tsi/empty-record-as-input) At src/Demo

Someone may correct me, but I think the issue is not the extension, but that the extension is a Method instead of a property. Currently filters only work on properties...

The way I solved it in one application is that I set the SomeEnumValue property whenever new data comes in and store the whole object together with it n memory...

For MSSQL server I think the default setting is a case insensitive comparison, but I guess we won't rely on that. I would assume that most people set there column...

And if we really just map IContains to Contains for EF and leave it up to the database configuration? We could see if anyone complains :-)

Is contains working for all of the database drivers used so far?

And what about converting it to a Linq expression first that compares both the field and the parameter to lower first?