spring-projects / spring-projects/spring-boot
Consider where to adopt records
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
We could use records for many of our configuration property classes. A number of classes that are used as DTOs by the actuator endpoints could probably also becomes records. https://github.com/spring-projects/spring-boot/issues/28074 is a prerequisite for using records for configuration properties.
I've labelled this as a task for now. It might become an epic or an enhancement depending on what we decide.
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 reviewing the configuration property classes and actuator endpoint DTOs mentioned in the issue, then read prerequisite issue #28074 to understand the record support dependency. The scope and completion criteria still need to be decided, including which classes are suitable for conversion and whether this should become an enhancement or epic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100