`TypeDiscoverer` uses single-level nesting for generics comparison about spring-data-commons HOT 3 CLOSED

Hi Team,
Do you have any solution for this issue?

from spring-data-commons.

This looks like a Spring Data Commons issue as we're creating the entity for DataBase using a type descriptor of com.example.demo.model.DataBase<java.util.List<java.util.Map<java.lang.String, java.math.BigDecimal>>> (instead of com.example.demo.model.DataBase<?> or even com.example.demo.model.DataBase) so I'm moving the ticket into Commons.

Another aspect is that we work on an Entity level. Component types are only retained for collections and map types, but not for custom types as a type of Foo<T> or Foo<Foo<T>> refers to the type Foo and during creation of the type, we do not have access to the enclosing context anymore.

from spring-data-commons.

The problem comes from TypeDiscoverer that resolves generics to a Class and then compares classes for equality. Reducing the type to Class erases the inner parameters (MyContainer<List<String>> vs MyContainer<List<Map<…>>) to List.class for both cases and therefore, the comparison falsely matches.

from spring-data-commons.