Allow `exactNumberMatch` and `maximumNumberMatch` in CoveringQuery
Open
type:enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
### Description
Currently only `minimumNumberMatch` is an option.
Contributor guide
Research direction
Start by locating CoveringQuery and reading how its existing minimumNumberMatch option is implemented. The issue names no files or tests; done means supporting exactNumberMatch and maximumNumberMatch alongside the current option, with behavior verified by the relevant test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100