spring-cloud / spring-cloud/spring-cloud-stream
Address fallback logic since SPR-17503 was resolved
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 646
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 8
Description
In the comment I noticed this line:
In all, all this will be obsolete once https://jira.spring.io/browse/SPR-17503
* is addressed and we can fall back on core resolvers
Please note that SPR-17503 was fixed back in 2019.
If that comment is still valid comment, please apply the final solution here.
Contributor guide
No contributing guide indexed for this repository
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 in spring-cloud-stream/src/main/java/org/springframework/cloud/stream/config/BinderFactoryAutoConfiguration.java around line 135. Review the fallback logic and the comment referring to SPR-17503, then verify what was resolved in that issue. Done means the obsolete workaround or reference is addressed consistently with the resolved core resolver behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100