@style.route and @requirer.requires should work correctly in either order
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Python
- Stars
- 838
- Forks
- 123
- Avg merge
- 7h 58m
- Merged PRs (30d)
- 12
Description
As seen in https://github.com/twisted/klein/pull/350 (and related ticket), @style.route has to be inside @requirer.require.
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 pull request 350 and the related ticket referenced in the issue, then reproduce both decorator orders in the relevant Klein routing and requirement examples or tests. Done means @style.route and @requirer.requires behave correctly regardless of which decorator is applied first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100