restify / restify/node-restify
req.path should be a property not a function
Open
Nobody has claimed this yet.
Critical
Feature
- 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
Feature Request
Use Case
Why do you want this?
req.path sets the expectation of being a value, however it is currently a function. This can be a jarring experience for developers.
Example API
This should include code snippets and documentation for the proposed feature
> req.path
/foo/bar
Are you willing and able to implement this?
"Yes" or, if "no", what can current contributors do to help you create a PR?
Yes
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 searching the restify source for the req.path implementation and its existing callers. Trace the request API tests, if present, and confirm the documented example works as req.path without invocation, returning the expected path such as /foo/bar.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100