Skip to content

[typespec-vscode] emitter's options as comment when updating tspconfig file #7691

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mzhongl524
Copy link
Member

Fix: #5621

Include emitter's options as comment when updating tspconfig.yaml with user selected emitter in CodeGeneration scenario

…h user selected emitter in CodeGeneration scenario
@mzhongl524 mzhongl524 added the ide Issues for VS, VSCode, Monaco, etc. label Jun 20, 2025
@mzhongl524 mzhongl524 marked this pull request as draft June 20, 2025 03:28
Copy link
Contributor

❌ There is undocummented changes. Run chronus add to add a changeset or click here.

The following packages have changes but are not documented.

  • typespec-vscode
Show changes

@azure-sdk
Copy link
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ide Issues for VS, VSCode, Monaco, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[vscode] Include emitter's options as comment when updating tspconfig.yaml with user selected emitter in CodeGeneration scenario
2 participants