restify / restify/node-restify
8to9 guide anti-documents removed re-routing feature
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.7k
- Forks
- 975
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 5
Description
- Used appropriate template for the issue type
- Searched both open and closed issues for duplicates of this issue
- Title adequately and concisely reflects the feature or the bug
Restify Version: 9
Node.js Version: 16
Expected behaviour
The 8to9 guide should provide help & assistance for people affected by #1847, the removal of re-routing.
Actual behaviour
The 8to9 guide falsly says re-routing works in 9.0 async handlers. And implies it is still available for classic handlers.
Repro case
Cause
Are you willing and able to fix this?
If I knew what the go-forward path was & how to migrate, I'd gladly submit a PR to update 8to9 guide.
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 with docs/guides/8to9guide.md around the linked re-routing section, then read issue #1847 to understand the removal and migration expectations. Update the 8to9 guide so it does not claim re-routing remains available for async or classic handlers and clearly reflects the supported go-forward path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100