Invalid

[waileong]

Invalid

[christophstrobl]

Thank you for reaching out - have you actually tried to verify the issue you so carefully crafted by throwing AI at it?
If you'd have, you'd have seen that the mapping layer operates up domain type field names to be able to apply potential field conversions. Those include explicit field type mappings as well as transforming the field name into its desired value.
So the actual query that hits the MongoDB server will use the correct field name.

This is part of how the repository abstraction works (in both AOT and non AOT mode) and interacts with other components.

So please, if you (an I really mean you as a human individual) think you found a bug worth reporting and would like us to spend some time investigating, please take the time to provide a complete minimal sample (something that we can unzip or git clone, build, and deploy) that reproduces the problem.

Having that said, I still might be missing something here. So if you think that's the case feel free to provide the requested sample containing a findByMyField method that does not fetch the desired documents from the database because the field names are incorrect.