`timedOut` instead of `timedout`?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, nodejs
- Domain
- backend
Research direction
The issue names no files or tests. Start by reviewing the middleware API and current timedout behavior, then clarify whether a rename or an opt-in option is intended; done means the agreed API change is implemented and tested.
Written by the indexing model from the issue text.
Description
timedout is hard to read and looks out of place next to headersSent, statusCode, lastModified etc.
Would it make sense to rename it, or at least add an option to rename it? I could implement and test it and make a PR.
- Dominant language
- JavaScript
- Stars
- 320
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
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.
More from expressjs/timeout
-
Upgrade Dependencies Open
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
-
discuss ideas
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in expressjs/timeout
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100