Skip to content

Conversation

@knutwannheden
Copy link
Contributor

When the actual type (e.g. Map, Optional, Collection) has
wildcard type parameters, the dedicated assertion methods may not accept
concrete arguments due to captured wildcards. Skip the transformation
whenever the dedicated assertion takes arguments and the actual type
has any wildcard type parameters.

…pe parameters

When the actual type (e.g. Map<?, ?>, Optional<?>, Collection<?>) has
wildcard type parameters, the dedicated assertion methods may not accept
concrete arguments due to captured wildcards. Skip the transformation
whenever the dedicated assertion takes arguments and the actual type
has any wildcard type parameters.
@github-project-automation github-project-automation bot moved this from In Progress to Ready to Review in OpenRewrite Feb 1, 2026
@timtebeek timtebeek merged commit 3a67bb9 into main Feb 1, 2026
2 checks passed
@timtebeek timtebeek deleted the fix/assertj-wildcard-and-withMessage branch February 1, 2026 07:35
@github-project-automation github-project-automation bot moved this from Ready to Review to Done in OpenRewrite Feb 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants