spring-cloud / spring-cloud/spring-cloud-commons
Priority of registering Configuration in NamedContextFactory
Open
Nobody has claimed this yet.
waiting-for-triage
- Dominant language
- Java
- Stars
- 751
- Forks
- 744
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
Why do you register a default Configuration later, so that the default Configuration will override a specific Configuration and increase the priority of the default Configuration?
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 NamedContextFactory's registration order for the default Configuration and a specific Configuration. Review the attached image and inspect where priority is assigned or resolved; done means explaining whether the default Configuration incorrectly overrides the specific one and identifying the relevant behavior to change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100