[SDK ask] we should force typespec conversion without vertical changes
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 115
Description
For vertical change definition, refer to [TypeSpec Brownfields Conversion (Specification)](https://microsoft-my.sharepoint.com/:w:/r/personal/mattge_microsoft_com1/_layouts/15/Doc.aspx?sourcedoc=%7B57BAE71D-CCE9-446C-AD6D-B0A314B628C1%7D&file=TypeSpec%20Brownfields%20Conversion%20Specification.docx&action=default&mobileredirect=true&share=IQEd57pX6cxsRK1tsKMUtijBAUWaqqhv4lqD384_DZ1knC4). We should ensure no vertical changes when brownfield service is working on TypeSpec conversion, by ensure
1. The TypeSpec conversion should be implemented in the latest stable version. This means that the latest stable version needs to be rewritten using TypeSpec.
2. The rewritten of the latest stable version should introduce no functional breaking changes.
Contributor guide
Research direction
No source file, test, or entry point is named. Start by reading the linked TypeSpec Brownfields Conversion specification, then locate the conversion workflow in this repository. Done means the latest stable version is rewritten using TypeSpec without functional breaking changes or vertical changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100