mapstruct / mapstruct/mapstruct
Raise error if qualifiedBy does not result in any match
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 7.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Currently, if you specify `qualifiedBy=..` and the methods passed into the `QualifierSelector` are all filtered out, we return the original list of methods.
Instead, we should raise an error statiing that no method qualifies for the given qualifiers.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at QualifierSelector and trace how qualifiedBy filtering currently falls back to the original methods. Done means the no-match case reports an error for the supplied qualifiers while normal matching remains unchanged; add focused coverage for both paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100