spring-cloud / spring-cloud/spring-cloud-gateway
Investigate using classes and techniques from AbstractHandlerMethodMapping
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Gateway server webmvc uses a custom invoker package to call methods for predicates and filters when configured via external configuration. It was copied from boots actuator support. This requires that filter and predicates be static methods (which are also used as a DSL).
If we use the classes and techniques from AbstractHandlerMethodMapping, we could have them potentially be beans.
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 reading AbstractHandlerMethodMapping at the linked Spring Framework location, then inspect Gateway WebMVC's custom invoker package and its use for externally configured predicates and filters. Done means determining whether those classes and techniques can replace the copied actuator support and allow the methods to be beans rather than static methods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100