spring-projects / spring-projects/spring-hateoas
Creating dynamic affordance
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 476
- PR merge metrics
- No merged PRs in 30d
Description
Hi @odrotbohm
We are using HAL Forms in our project and we need to know how to dynamically generate the affordance.
We have lot of settings in our project and it can be changed dynamically. For ex, consider there is a property named "name" and whether it should be made mandatory or optional is based on the setting. If the setting is true, then "name" is mandatory and vice-versa. In this case, how can we dynamically set the "required" flag to true or false based on setting value?
PS: Also, please note that settings can be changed at runtime. We will work on to get the modified setting value.
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 source file, test, or entry point. Start by tracing Spring HATEOAS's HAL Forms affordance API and how it handles the required flag, then examine how runtime setting changes could reach that API. Done means establishing a supported approach for dynamically determining whether a property is required, with its behavior verified or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100