microsoft / microsoft/DefinitelyTyped-tools
Non-newest version should be allowed at top-level
Open
Nobody has claimed this yet.
publisher
- Dominant language
- TypeScript
- Stars
- 423
- Forks
- 237
- Avg merge
- 18h 18m
- Merged PRs (30d)
- 11
Description
To support betas, it would be nice to allow, for example, a v7 directory while the main directory stays at an earlier version.
- The main directory should retain the
latesttag. - It would also make it clearer to contributors which are the main typings to contribute to.
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
The issue names no files, tests, or entry points. Start by locating the repository logic that determines the top-level version and assigns the latest tag. Done means a top-level v7 directory can coexist with an earlier main version, the main directory retains latest, and contributors can distinguish the primary typings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100