spring-projects / spring-projects/spring-hateoas
Support JSpecify to determine if a property is required or not
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 476
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
We moved to JSpecify but it looks like Spring HATEOAS doesn't consider it when determining if a property is required or not. Looks like this is currently based on jakarta validation only.
Could JSpecify support be added for this?
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
The issue names no files or tests; start by locating the code that currently uses Jakarta Validation to determine whether a property is required, then inspect how JSpecify annotations should be recognized. Done means JSpecify nullness information is considered alongside the existing validation-based behavior, with tests covering required and non-required properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100