Unify CallableResolver and AdvancedCallableResolver
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 12.3k
- Forks
- 2k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 6
Description
Since AdvancedCallableResolver was introduced midway through the release of Slim 4, we will need to unify the two interfaces in Slim 5 and break everything moving forward.
We will also need to ensure that the CallableResolverInterface::resolve() method throws a named exception instead of RuntimeException so downstream implementers can effectively control the execution flow.
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 locating AdvancedCallableResolver, CallableResolverInterface, and the implementations of CallableResolverInterface::resolve(). Review how the two interfaces differ and how RuntimeException is currently handled. Done means the resolver interfaces are unified for Slim 5 and resolve() uses a named exception with downstream behavior covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100