spring-projects / spring-projects/spring-hateoas
Allow to define HAL FORMS options based on the representation model's state
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 476
- PR merge metrics
- No merged PRs in 30d
Description
At the moment options can only be added via HalFormsConfiguration for certain input classes' properties.
It would be more flexible when PropertyMetadata would support it too, because there are use cases where a class and property based approach is not sufficient:
- Dependent on a certain state only a subset of options are allowed: order amount > 1000 $ -> shipping only via UPS, not via FedEx
- List/Array types: property or Parameter of type List
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 with HalFormsConfiguration and PropertyMetadata, then trace how input-class properties become HAL FORMS options. Verify the design covers state-dependent option subsets and List properties, with tests demonstrating both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100