Cache for mapped property names

[SergerGood]

The cache in PropertyCache has been extended to work with case insensitive mappedNames. This made it possible to reduce the search for properties and allocation of memory.

[SergerGood]

oops, I think I broke something

[mikependon]

Hey, it is a nice optimization. Any particular reason why does the test suites fail?

[SergerGood]

Some tests failed. Now I'll see what went wrong

[SergerGood]

https://github.com/mikependon/RepoDB/blob/9ec4d8e09a711786d58d27ea1d682e3ef90aa01b/RepoDb/RepoDb.Tests/RepoDb.UnitTests/QueryGroups/QueryGroupParseExpressionClassesTest.cs#L25

https://github.com/mikependon/RepoDB/blob/9ec4d8e09a711786d58d27ea1d682e3ef90aa01b/RepoDb/RepoDb.Tests/RepoDb.UnitTests/QueryGroups/QueryGroupParseExpressionClassesTest.cs#L33

I made a dictionary for the mapped names, but there is a duplicate name here. I think that this is not correct, especially considering the old logic FirstOrDefault

[SergerGood]

Mapping calls the PropertyCache at generation time. Therefore, it cannot be called before the mapping itself. I added a separate cache for mappedNames, which is called for individual properties.

[SergerGood]

https://github.com/mikependon/RepoDB/blob/9ec4d8e09a711786d58d27ea1d682e3ef90aa01b/RepoDb/RepoDb.Tests/RepoDb.UnitTests/QueryGroups/QueryGroupParseExpressionClassesTest.cs#L25

https://github.com/mikependon/RepoDB/blob/9ec4d8e09a711786d58d27ea1d682e3ef90aa01b/RepoDb/RepoDb.Tests/RepoDb.UnitTests/QueryGroups/QueryGroupParseExpressionClassesTest.cs#L33

I made a dictionary for the mapped names, but there is a duplicate name here. I think that this is not correct, especially considering the old logic FirstOrDefault

What about this?

[SergerGood]

https://github.com/mikependon/RepoDB/blob/9ec4d8e09a711786d58d27ea1d682e3ef90aa01b/RepoDb.Core/RepoDb.Tests/RepoDb.IntegrationTests/PropertyHandlerImplicitTest.cs#L50 PropertyHandler Also calls mappedNames during mapping...

[SergerGood]

I left the PropertyCache alone. The PropertyHandler logic is designed for the fact that we will iterate over the properties and, accordingly, map them one by one.

So I added the MappedPropertyCache which works with the PropertyCache. And called him in places where you really need to work with mapped properties.

But problem of duplicate name still left. As designed?

[mikependon]

Just to give you updates, I am still reviewing this.