spring-projects / spring-projects/spring-hateoas
Investigate more fluent alternative for LinkDiscoverer
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 476
- PR merge metrics
- No merged PRs in 30d
Description
LinkDiscoverer currently combines link lookups from four dimensions:
- Link relations as
StringandLinkRelation. - Represenation sources as
StringandInputStream. - Lookups of one optional link, one mandatory one and multiple links.
That makes the number of methods in the interface explode quite a bit. Although most of the variants can be mitigated via default methods a slightly more fluent variant would be neat while we could still keep the convenient SPI interface for media type implementors.
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 the LinkDiscoverer interface and map its four lookup dimensions: relation type, representation source, and optional, mandatory, or multiple links. Investigate a fluent alternative while preserving the convenient SPI interface for media type implementors. Done means a concrete API direction is established for reducing method combinations without losing the existing SPI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100