spring-projects / spring-projects/spring-boot
Use consistent binder when calling both resolve and resolveProfileSpecific in ConfigDataLocationResolver
Open
Nobody has claimed this yet.
status: pending-design-work
type: enhancement
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
See #43514 for an example of the problem not passing the same binder in can cause. I think that not allowing profile specific config data to be resolved might help.
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 at ConfigDataLocationResolver and compare the binder used by resolve with the binder used by resolveProfileSpecific. Read issue #43514 for the reported failure, then determine whether profile-specific config data should remain resolvable and verify that both resolution paths use the same binder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100