spring-projects / spring-projects/spring-data-relational
Refine collection-like property conversion using arrays
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 827
- Forks
- 394
- PR merge metrics
- No merged PRs in 30d
Description
We have multiple places that deal with array conversion also outside of the converter. That isn't ideal as array handling is distributed across the code base. Also, we do not properly convert individual array values, instead we use the conversion service to convert one array into another. Array-to-array conversion causes an inconsistency across modules as we should apply converters on a per-element level.
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 tracing the array-handling code outside the converter and the conversion service that currently converts one array into another. Map the affected modules and existing converter entry points first; done means array handling is centralized and individual array values follow the same conversion path consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100