-
Notifications
You must be signed in to change notification settings - Fork 294
[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
base: main
Are you sure you want to change the base?
[typespec-vscode] emitter's options as comment when updating tspconfig file #7691
Conversation
…h user selected emitter in CodeGeneration scenario
All changed packages have been documented.
|
You can try these changes here
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you share a gif of what this looks like? Does it keep adding the options even if we delete them?
Do we really feel like this is valuable now that we have auto complete in the config? This just feels like noise to me. Only time I would see this being valuable is in the init flow
Fix: #5621
Include emitter's options as comment when updating
tspconfig.yaml
with user selected emitter inCodeGeneration
scenario