-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mitigate gaps for common types between swagger and typespec #2335
Comments
For 1, 2, 3 we have issues tracked. For 4 this is introduced by design because we move ErrorResponse to core. For 5 both are modeled as extensible enum but modular name is createdByType but hlc is CreatedByType(normailized). |
For 6 in swagger we could specify the required or optional in For example the DataProduct type didn't specify any required properties in swagger. So all properties are optional. In typespec the id and type are required by default so the type DataProduct would have them as required https://github.com/Azure/azure-sdk-for-js/pull/28812/files#r1519701904. |
One workaround is to override the definition in sub types. tracked here: Azure/typespec-azure#401 |
Add |
need to upgrade the typespec compiler version and verify it. |
Updated as May 20,
|
2 fixed |
Close this one considering there is no breaking introduced by common types. |
the item 7 is tracked here #2535 |
No description provided.
The text was updated successfully, but these errors were encountered: