The properties FirstName and First_Name are ambiguous. Dapper (core, haven't checked AOT) prefers properties over fields, but there was a glitch where ambiguous properties could get conflated.
We should warn if:
any two fields on the same type have the same name after normalisation
any two properties on the same type have the same name after normalisation
We should also verify that AOT prefers properties over fields (this isn't a warning: this is a library requirement)
See https://github.com/DapperLib/Dapper/issues/1993
The properties
FirstNameandFirst_Nameare ambiguous. Dapper (core, haven't checked AOT) prefers properties over fields, but there was a glitch where ambiguous properties could get conflated.We should warn if:
We should also verify that AOT prefers properties over fields (this isn't a warning: this is a library requirement)
This analyzer applies with+without AOT enabled.