Skip to content
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

Fixed resolving generic types for vavr maps. #2517

Closed

Conversation

nexx512
Copy link

@nexx512 nexx512 commented Dec 17, 2021

Currently the generic types of vavr maps are not detected correctly. This should be fixed with this PR.

@nexx512
Copy link
Author

nexx512 commented Feb 7, 2022

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.

odrotbohm pushed a commit that referenced this pull request Feb 14, 2022
odrotbohm added a commit that referenced this pull request Feb 14, 2022
Reorder methods according to conventions. More speaking names for the newly introduced type lookup methods.

Issue #2517.
odrotbohm pushed a commit that referenced this pull request Feb 14, 2022
odrotbohm added a commit that referenced this pull request Feb 14, 2022
Reorder methods according to conventions. More speaking names for the newly introduced type lookup methods.

Issue #2517.
@odrotbohm
Copy link
Member

That's applied. See my comment on #2511 for details.

@odrotbohm odrotbohm added in: core Issues in core support and removed status: waiting-for-triage An issue we've not yet triaged labels Feb 16, 2022
@odrotbohm odrotbohm added this to the 2.7 M3 (2021.2.0) milestone Feb 16, 2022
@odrotbohm odrotbohm self-assigned this Feb 16, 2022
@odrotbohm odrotbohm closed this Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants