Unsupported Repository query return types have no hints or logs or exceptions

[FULaBUla]

As I reported in #3379, the query still succeeds and returns when an unsupported type is used, but an exception occurs when I use this object of the type I defined. In my opinion, the type should be checked and prompted at the time of use or startup.

[jack5505]

Guys I didn't understand that issue has opened #3379 in this is closed but here is registered as enhancement. Should I take to work on this issue

[FULaBUla]

Guys I didn't understand that issue has opened #3379 in this is closed but here is registered as enhancement. Should I take to work on this issue

please see this url: #3379 (comment) , I think an enhancement is needed to make it easier to throw exceptions or print logs to note unsupported return types. It is not very friendly to throw an exception when the result is returned with the wrong type but only when used

[mp911de]

Queries can return all sorts of weird types and we cannot reliably know what is supported and what not because queries can be quite dynamic. If you're looking for support for a specific type, please file a ticket along with a bit of code so that we can get an idea what you're trying to achieve.

Descritpions like #3379 (comment) aren't helpful as they only say what is not working but not what you're trying to achieve.

[FULaBUla]

I want a hint or exception message about the inconsistency between the declared generics and the returned generics. For example, if I declare Page<List>, but page.getContent () returns Object[], List and Object[] are two different types, I should get a hint or an exception
@mp911de