next_ should not be available for injection into commands
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
raise an error, helps disambiguate middlewares (maybe automatically turn it into middleware? probs too magical)
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 by locating the command injection and `next_` handling in the repository, then inspect any tests covering middleware or command dispatch. The change is complete when injecting `next_` into commands raises an error and the relevant behavior is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100