Skip to content
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

[Playwright-DevDiv-Service - Playwright] API Review #31794

Open
azure-sdk opened this issue Dec 6, 2024 · 6 comments · May be fixed by #31855
Open

[Playwright-DevDiv-Service - Playwright] API Review #31794

azure-sdk opened this issue Dec 6, 2024 · 6 comments · May be fixed by #31855
Labels
API Review Scoping This is an issue that will track work on a specific set of API changes.

Comments

@azure-sdk
Copy link
Collaborator

New API Review meeting has been requested.

Service Name: Playwright-DevDiv-Service - Playwright
Review Created By: Vansh Singh
Review Date: 01/15/2025 09:00 AM PT
Release Plan: 1533
PR:
Hero Scenarios Link: here
Core Concepts Doc Link: here

Description:

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

@azure-sdk azure-sdk added the API Review Scoping This is an issue that will track work on a specific set of API changes. label Dec 6, 2024
@azure-sdk
Copy link
Collaborator Author

Meeting updated by Manivelu Rajendran

Service Name: Playwright-DevDiv-Service - Playwright
Review Created By: Vansh Singh
Review Date: 01/15/2025 09:00 AM PT
Release Plan: 1533
PR:
Hero Scenarios Link: here
Core Concepts Doc Link: here

Description: TBD

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

@mjmadhu
Copy link
Member

mjmadhu commented Dec 13, 2024

Current PR for review - #31855

We had a thread opened earlier for similar changes with preview version that got closed with unmerged commits unfortunately (due to long absence from our side). We'd like to reactivate this discussion again as the GA for our product is planned next month. The PR was signed off though.

Madhuri Jain: Data Plane API Review Request for new api-version
posted in Azure API Stewardship Board / General on Thursday, May 30, 2024 11:51 AM

Old PR -
Release playwrighttesting microsoft.playwright testing preview/2024 06 01 preview by mjmadhu · Pull Request #29262 · Azure/azure-rest-api-specs

P.S. - We've an upcoming PR for another data plane service for the same product shortly.

@mikekistler
Copy link
Member

@mjmadhu Please post in the Service API Toolset Teams channel to request help with whatever validation problems you are having with the existing branch.

@mjmadhu
Copy link
Member

mjmadhu commented Dec 17, 2024

The TypeSpec Validation error is fixed now. Thanks @mikeharder for guiding there.
The Swagger LintDiff error is due to non standard HTTP response code 302 used in our API which was discussed in the context of previous PR earlier as a product requirement scenario and was signed off earlier.
Please help with further review and next steps to merge.

@mikeharder
Copy link
Member

The TypeSpec Validation error is fixed now. Thanks @mikeharder for guiding there. The Swagger LintDiff error is due to non standard HTTP response code 302 used in our API which was discussed in the context of previous PR earlier as a product requirement scenario and was signed off earlier. Please help with further review and next steps to merge.

For LintDiff, you need to add a suppression to your readme.md. If this was signed off earlier, the suppression should have been added to your readme.md at that time.

https://eng.ms/docs/products/azure-developer-experience/design/specs-pr-guides/pr-suppressions#suppress-autorest-extension

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Review Scoping This is an issue that will track work on a specific set of API changes.
Projects
Status: Triage
4 participants