VerifiableProperties needs more APIs
Open
Nobody has claimed this yet.
enhancement
newbie
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
VerifiableProperties needs a few more APIs to support the use cases that have cropped.
- a "get if positive, otherwise throw" function for all types
- also provide separate functions for min and max bounds (for ranges)
Contributor guide
No contributing guide indexed for this repository
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 by locating the VerifiableProperties class and reading its existing accessor APIs and related tests. Compare the current range and validation behavior across supported types, then identify the tests that should cover positive-only access and separate minimum and maximum bounds. Done means the requested APIs are available consistently for all supported types and their behavior is tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100