Add TypeSpec requirement validation in release plans
Open
Engagement Experience
TypeSpec
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
Currently, a release plan includes information about TypeSpec. It is not until the user creates the API spec PR that they get an error when they do a REST API in Open API instead of TypeSpec.
We should look into a way to add validation earlier in the process and stop users before they spend time working on their OpenAPI spec.
Contributor guide
Assessment
This issue has not been assessed yet.