Test TypeSpec API review gen

[praveenkuttappan]

test creating API review for contoso test typespec project

[openapi-pipeline-app-test]

Swagger pipeline restarted successfully, please wait for status update in this comment.

[workflow-bot-test]

Hi, @praveenkuttappan Thanks for your PR. I am workflow bot for review process. Here are some small tips.

Please ensure to do self-check against checklists in first PR comment.

PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.

For specs comparison cross API versions, Use API Specs Comparison Report Generator

If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

Any feedback about review process or workflow bot, pls contact swagger and tools team. vscswagger@microsoft.com

[openapi-pipeline-app-test]

Swagger Generation Artifacts

️🔄~[Staging] ApiDocPreview inProgress [Detail]

️⌛ azure-sdk-for-python pending [Detail]

️⌛ azure-sdk-for-net-track2 pending [Detail]

️🔄 azure-sdk-for-js inProgress [Detail]

️⌛ azure-sdk-for-java pending [Detail]

_{Posted by Swagger Pipeline | How to fix these errors?}

[openapi-pipeline-app-test]

Swagger pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

[workflow-bot-test]

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.
Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
If you want to know the production traffic statistic, please see ARM Traffic statistic.
If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.
Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.

[workflow-bot-test]

Hi @praveenkuttappan, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff. If you have any questions, please post your questions in this channel https://aka.ms/swaggersupport.

Task	How to fix	Priority
Avocado	Fix-Avocado	High
Semantic validation	Fix-SemanticValidation-Error	High
Model validation	Fix-ModelValidation-Error	High
LintDiff	Fix-LintDiff	high

If you need further help, please feedback via swagger feedback.

[praveenkuttappan]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.