Conversation
|
Hi, @osaghaso 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 |
|---|---|---|
| AzureCommunicationServices.json | 2018-01-01(02e9ba1) | 2018-01-01(main) |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 2 Warnings warning [Detail]
| compared tags (via openapi-validator v2.1.6) | new version | base version |
|---|---|---|
| package-2023-06-01-preview | package-2023-06-01-preview(02e9ba1) | package-2023-06-01-preview(main) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L343 |
||
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L467 |
The following errors/warnings exist before current PR submission:
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
|
Hi @osaghaso, Your PR has some issues. Please fix the CI sequentially by following the order of
|
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Outdated
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Outdated
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Outdated
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Outdated
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Show resolved
Hide resolved
| } | ||
| ], | ||
| "properties": { | ||
| "queueInfo": { |
There was a problem hiding this comment.
Can this still be renamed? If so we should use queueDetails. If not we can add "x-ms-client-name" and set it to queueDetails.
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Outdated
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Outdated
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Show resolved
Hide resolved
...entgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
Outdated
Show resolved
Hide resolved
|
There are conflicts from preventing this from being merged, and since this is going to main, that means it's ready for a final review. Have you scheduled a review with the REST API Stewardship Board? Otherwise, if it's a work in progress, you should use a feature branch. See https://eng.ms/docs/products/azure-developer-experience/onboard/requirements. |
These events have already been reviewed by the arch board - they don't go through a REST API review. |
|
Swagger pipeline restarted successfully, please wait for status update in this comment. |
Data Plane API - Pull Request
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.
Is this review for (select one):
link to Schema
Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.
❔Got questions? Need additional info?? We are here to help!
Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.
Click here for links to tools, specs, guidelines & other good stuff
Tooling
Guidelines & Specifications
Helpful Links