Add references to possible discussions about upstreaming this
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- documentation
Research direction
Review the repository history and any existing documentation for the rationale behind the methods not being exposed upstream. Find the relevant discussions or TypeScript team positions, then document those references and the stated long-term goal of avoiding a maintained fork.
Written by the indexing model from the issue text.
Description
For someone who haven't followed the history of tsd it would be neat to have it documented here why these methods hasn't been exposed upstream – if there's eg. an opposition from the TypeScript team to them or if there's something else blocking it.
I guess long term goal is to not have to maintain a fork like this?
(Also: Sorry for jumping on here with an issue this quickly, I understand it might be premature, not trying to stress you out or anything, just want to be helpful 🙂)
- Dominant language
- JavaScript
- Stars
- 29
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
Similar issues
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
blamechris/chroxy#8579 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
modusensus/dsh-mneme#411 ·
-
Flaky (suspected): VideoTimelineEditor bed audio test sees 600px instead of 120px under CI loadOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Actions on ToastsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nextcloud-libraries/nextcloud-dialogs#2669 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
XRPLF/xrpl-dev-portal#4000 ·
Maintainers usually reply within 1 day