Verify type spec api review gen#2921
Conversation
|
Hi, @praveenkuttappan Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vscswagger@microsoft.com |
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| widgets.json | 2022-11-01-preview(39e217b) | 2022-11-01-preview(main) |
| Rule | Message |
|---|---|
1033 - RemovedProperty |
The new version is missing a property found in the old version. Was 'widgetName' renamed or removed? New: Azure.Contoso.WidgetManager/preview/2022-11-01-preview/widgets.json#L296:15 Old: Azure.Contoso.WidgetManager/preview/2022-11-01-preview/widgets.json#L272:15 |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️LintDiff succeeded [Detail] [Expand]
Validation passes for LintDiff.
️️✔️~[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]
API Test is not triggered due to precheck failure. Check pipeline log for details.
️❌SwaggerAPIView: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
Failed to generate swagger APIView. The readme file format is invalid and the tag is not defined. Use the provided readme template for guidance readme template. For more details, please check the detail log. |
"How to fix":"Check the readme file and make sure the readme file format is valid and the tag is defined. Use the provided readme template" |
️️✔️CadlAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️❌Avocado: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
MISSING_README |
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: data-plane/Azure.Contoso.WidgetManager/preview/2022-11-01-preview |
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️❌~[Staging] PrettierCheck: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
HowToFix |
Code style issues found path: Azure.Contoso.WidgetManager/preview/2022-11-01-preview/widgets.json |
️️✔️~[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️PR Summary succeeded [Detail] [Expand]
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️❌TypeSpec Validation: 13 Errors, 28 Warnings failed [Detail]
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
unknown-identifier |
Unknown identifier Cadl Location: specification/cognitiveservices/OpenAI.Authoring/model.routes.tsp#L9 |
unknown-identifier |
Unknown identifier Cadl Location: specification/cognitiveservices/OpenAI.Authoring/model.routes.tsp#L10 |
unknown-identifier |
Unknown identifier Cadl Location: specification/cognitiveservices/OpenAI.Authoring/finetune.tsp#L93 |
unknown-decorator |
Unknown decorator Location: specification/cognitiveservices/OpenAI.Authoring/finetune.tsp#L93 |
unknown-identifier |
Unknown identifier route Location: specification/cognitiveservices/OpenAI.Authoring/model.routes.tsp#L27 |
unknown-decorator |
Unknown decorator Location: specification/cognitiveservices/OpenAI.Authoring/model.routes.tsp#L27 |
unknown-identifier |
Unknown identifier get Location: specification/cognitiveservices/OpenAI.Authoring/model.routes.tsp#L28 |
unknown-decorator |
Unknown decorator Location: specification/cognitiveservices/OpenAI.Authoring/model.routes.tsp#L28 |
GeneratedSwaggerNotFound |
"details":"The generated swagger file from typespec specification/contosowidgetmanager/Contoso.WidgetManager can not be found." |
InConsistentSwagger |
"details":"The generated swagger file v1.1/openapi.json from typespec specification/cognitiveservices/AnomalyDetector is not the same as the '/mnt/vss/_work/1/azure-rest-api-specs/specification/cognitiveservices/data-plane/AnomalyDetector/stable/v1.1/openapi.json' in PR, please make sure the swagger is consistent with the generated swagger. You can find the difference in the pipeline log." |
MissingExamplesDirectory |
"details":"The 'examples' directory is missing in the typespec folder specification/cognitiveservices/OpenAI.Authoring, please ensure the 'examples' is added in the PR." |
MissingExamplesDirectory |
"details":"The 'examples' directory is missing in the typespec folder specification/cognitiveservices/OpenAI.Inference, please ensure the 'examples' is added in the PR." |
InConsistentSwagger |
"details":"The generated swagger file v1.1/openapi.json from typespec specification/cognitiveservices/OpenAI.Inference is not the same as the '/mnt/vss/_work/1/azure-rest-api-specs/specification/cognitiveservices/data-plane/AnomalyDetector/stable/v1.1/openapi.json' in PR, please make sure the swagger is consistent with the generated swagger. You can find the difference in the pipeline log." |
Enums should be defined without the @fixed decorator.Location: cognitiveservices/AnomalyDetector/univariate/models.tsp#L34 |
|
| The names of Property types must use camelCase Location: cognitiveservices/AnomalyDetector/univariate/models.tsp#L176 |
|
| Operation 'DetectUnivariateEntireSeries' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/univariate/routes.tsp#L11 |
|
| Operation 'DetectUnivariateLastPoint' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/univariate/routes.tsp#L26 |
|
| Operation 'DetectUnivariateChangePoint' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/univariate/routes.tsp#L39 |
|
Enums should be defined without the @fixed decorator.Location: cognitiveservices/AnomalyDetector/multivariate/models.tsp#L21 |
|
| The names of Property types must use camelCase Location: cognitiveservices/AnomalyDetector/multivariate/models.tsp#L100 |
|
| The names of Property types must use camelCase Location: cognitiveservices/AnomalyDetector/multivariate/models.tsp#L390 |
|
Enums should be defined without the @fixed decorator.Location: cognitiveservices/AnomalyDetector/multivariate/models.tsp#L37 |
|
| The names of Property types must use camelCase Location: cognitiveservices/AnomalyDetector/multivariate/models.tsp#L268 |
|
Enums should be defined without the @fixed decorator.Location: cognitiveservices/AnomalyDetector/multivariate/models.tsp#L43 |
|
| Operation 'GetMultivariateBatchDetectionResult' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/multivariate/routes.tsp#L11 |
|
| Operation 'TrainMultivariateModel' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/multivariate/routes.tsp#L26 |
|
| The names of Property types must use camelCase Location: cognitiveservices/AnomalyDetector/multivariate/routes.tsp#L44 |
|
| Operation 'ListMultivariateModels' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/multivariate/routes.tsp#L49 |
|
| Operation 'DeleteMultivariateModel' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/multivariate/routes.tsp#L65 |
|
| Operation 'GetMultivariateModel' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/multivariate/routes.tsp#L80 |
Swagger Generation Artifacts
|
Generated ApiView
|
|
Hi @praveenkuttappan, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
|
Hi @praveenkuttappan, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
/azp run |
|
No pipelines are associated with this pull request. |
Test TypeSpec APi review gen