jprichardson / jprichardson/node-nextflow
"next" word conflict
Open
Nobody has claimed this yet.
- Dominant language
- CoffeeScript
- Stars
- 39
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Hello.
next flow = ...
Conflicts with node's express convention
(req, res, next)
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 next flow = ... API and reviewing how it conflicts with Express callbacks using (req, res, next). Determine the intended naming change and identify the affected usage examples or tests. Done means the conflict is resolved without leaving the API change ambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- coffeescript, node.js
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100