Add references to possible discussions about upstreaming this
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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 🙂)
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
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.
Assessment
- Tech stack
- typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100