Improve TypeSpec versioning story
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 90
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 156
Description
Versioning feels like a detective's case map
- complex versioning library implementation
- usage limitations (limited target, renaming properties,)
- other usage concerns (Mario), complexity due to prolific versioning info vs simple SBS models, (particularly combined with other decorators such as visibility) to understand the end shape
- preview vs stable where preview features persist in preview versions only
Contributor guide
Research direction
The issue names no files or tests. Start by reviewing the versioning library and its current usage alongside SBS models and decorators such as visibility; compare the handling of preview and stable versions. The scope and acceptance criteria still need to be defined before completion can be assessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100