apache / apache/incubator-seata
optimize addConfigListener API usage
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
For the configuration center, there should be a unified configuration center entrance including getConfig, addConfigListener, etc. Here addConfigListener use the ConfigurationCache API, we should always use ConfigurationFactory. getInstance () and keep the function remains the same.
Contributor guide
Research direction
Start by locating addConfigListener and the ConfigurationCache and ConfigurationFactory APIs in the repository. Compare how the configuration-center entry points are used, then verify that addConfigListener uses ConfigurationFactory while preserving the existing function behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100