spring-projects / spring-projects/spring-framework
Introduce dedicated contract for contributing runtime hints for a bean
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 60.2k
- Forks
- 38.8k
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 27
Description
As discussed in https://github.com/spring-projects/spring-framework/issues/35500#issuecomment-3334284774 there is a desire to create a dedicated hook point for contributing runtime hints (and runtime hints only) for a bean.
Right now we use BeanRegistrationAotProcessor for the lack of a better option but the callback provides the whole code generation machinery that such implementations do not need. Having a dedicated callback should achieve the following:
- Ease unit testing as we only need to provide
RuntimeHints - Clarify the scope so that we can not invoke such implementations at all if runtime hints aren't required.
Contributor guide
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 reading the linked discussion and locating the current BeanRegistrationAotProcessor implementations that contribute runtime hints. Define the dedicated runtime-hints-only contract and update its integration so implementations receive RuntimeHints without the broader code-generation machinery. Done means unit tests can provide only RuntimeHints and hint-only implementations are skipped when runtime hints are not required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100