Add the remaining UI test case for Typespec Extension #7976
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
v-xuto
requested review from
RodgeFu,
lirenhe,
bterlson,
markcowl,
timotheeguerin,
chrisradek,
AlitzelMendez and
witemple-msft
as code owners
v-xuto
changed the title
|
All changed packages have been documented.
|
packages/typespec-vscode/test/extension/create-typespec.test.ts
Outdated
Show resolved
Hide resolved
…to add-test-case
This reverts commit 06b3c05.
|
@timotheeguerin PR is ready, please help review this PR. |
v-xuto
changed the title
|
@timotheeguerin The above comments have been resolved. This PR is ready, please help review this PR. Thanks. |
|
@markcowl Could you please help review this PR when you have time? Thank you in advance. |
RodgeFu
approved these changes
Aug 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add 4 UI test cases to typespec-vscode package in CI/CI pipeline.
Emit Client Code from TypeSpec - .NET- triggered by command palette - no emitter intspconfig.yamlEmit Client Code from TypeSpec - .NET- triggered by command palette - have emitter intspconfig.yaml, clickChoose another emitterImport TypeSpec from OpenAPI3- triggered by right click on folderPreview API Documentation- triggered by command palette