spring-projects / spring-projects/spring-hateoas
MessageResolver throws a NoSuchMessageException if a message cannot be resolved (and does not return null as mentioned in the javadoc)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 476
- PR merge metrics
- No merged PRs in 30d
Description
If one calls resolve on the MessageResolver and the message cannot be resolved, a NoSuchMessageException is thrown.
The javadoc of the resolve method explains that null is returned if no message was found. This is only true if the no resource bundles were found and the DefaultOnlyMessageResolver is configured through the HateoasConfiguration.
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 MessageResolver.resolve and the DefaultOnlyMessageResolver configuration described in the issue. Compare the resolve javadoc with the behavior when no message is found; done means the documented return behavior and actual behavior agree, with the relevant behavior covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100