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

[@typespec/spector] - Handle and report failed scenarios at the end #4872

Merged
merged 3 commits into from
Oct 26, 2024

Conversation

sarangan12
Copy link
Contributor

In the server-test scenario, if there is an error, then the script immediately reports the error and comes out of the execution. But, the service generator has not implemented all the scenarios yet. So, If all the scenarios are executed, then the script might fail even before executing the intended script. So, the correct approach would be to report at the end.

Please review and approve the PR. Thanks

@azure-sdk
Copy link
Collaborator

azure-sdk commented Oct 25, 2024

All changed packages have been documented.

  • @typespec/spector
Show changes

@typespec/spector - internal ✏️

Handle Failing scenarios at the end

@azure-sdk
Copy link
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 📚 Next docs

@sarangan12 sarangan12 added this pull request to the merge queue Oct 26, 2024
Merged via the queue into microsoft:main with commit 265c4fc Oct 26, 2024
22 checks passed
@sarangan12 sarangan12 deleted the FormatErrorOutput branch October 26, 2024 01:56
swatkatz pushed a commit to swatkatz/typespec that referenced this pull request Nov 5, 2024
…icrosoft#4872)

In the `server-test` scenario, if there is an error, then the script
immediately reports the error and comes out of the execution. But, the
service generator has not implemented all the scenarios yet. So, If all
the scenarios are executed, then the script might fail even before
executing the intended script. So, the correct approach would be to
report at the end.

Please review and approve the PR. Thanks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants