-
Notifications
You must be signed in to change notification settings - Fork 664
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistencies between isMap() and how the the type is treated #2539
Comments
Closing in favor of #2517. Even if not an exact duplicate, we need to cover the Vavr collections and maps story as a whole. |
Are there chances that this will be fixed soon? Right now we are stuck with Spring 2.5.x and can't update our project to newer Spring versions. |
Care to elaborate? Vavr |
Thank you for your explanation. I think there are a couple of issues that are a bit mixed up right now. Let me try to clarify this. I did send a couple merge requests regarding Vavr type mapping. These are meant for discussion. My main focus was not to implement Vavr object mapping in SD but to simplify the usage of custom type mappers (I refer to #3912 and #2511). But actually, this is not a problem for us right now. By writing a custom Mapper class derived from But now to the real issue we have: Right now we use Spring Boot 2.5.9. But when I update our project to Spring Boot 2.6.3 I get the error The change in #2517 class So for us the issue in So would it be possible to accept the changes in #2517 (or even only the changes in |
Class ParameterizedTypeInformation:
isMap() is true for Vavr maps but in some Function the type is treated like a java map.
See #2517 for more details
This leads to Problems with aggregates using vavr maps for mongodb
The text was updated successfully, but these errors were encountered: