spring-cloud / spring-cloud/spring-cloud-openfeign
FeignClientFactoryBean does not provide a way to register a ResponseMapper
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 838
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 13
Description
Feign provides an interface called ResponseMapper which allows you to do processing on a response before it is decoding. This is a useful extension for pre-processing things such as response headers without having to embed logic into your decoder. The FeignClientFactoryBean does not allow a mechanism to add one which forces consumers to abandon the auto configured feign client functionality and manually create the Feign client if they choose to take advantage of that feature. This request is simply to optionally allow a ResponseMapper to be exposed and included in the Feign client.
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 in FeignClientFactoryBean and inspect how the auto-configured Feign client is assembled. Read the Feign ResponseMapper interface and the surrounding client configuration to identify an optional registration path. Done means consumers can provide a ResponseMapper while continuing to use the auto-configured client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100