microsoft / microsoft/DefinitelyTyped-tools
No way to deprecate packages without a higher version of the source package
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 423
- Forks
- 237
- Avg merge
- 18h 18m
- Merged PRs (30d)
- 11
Description
For example, composer-concerto is at 0.71, as is @types/composer-concerto. But the source package has shipped its own types since 0.32! Right now, deprecation can't happen until composer-concerto adds a version that is 0.72 or higher.
We need a way to deprecate @types/composer-concerto as-is. Perhaps it would be OK to publish a deprecated 0.71.1, since presumably all users of the types also have the same version of the source package. But we'd need to think through the implications.
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
Start with the issue description and trace how package versions and deprecations are currently handled in DefinitelyTyped-tools. Compare the proposed deprecated 0.71.1 approach with the requirement to deprecate @types/composer-concerto at its current version. Done means an agreed, documented mechanism that accounts for the source package version implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100