Skip to content

Conversation

@sheetalkamat
Copy link
Member

Fixes #30739

@typescript-bot
Copy link
Collaborator

Thanks for the PR! It looks like you've changed the TSServer protocol in some way. Please ensure that any changes here don't break consumers of the current TSServer API. For some extra review, we'll ping @sheetalkamat, @amcasey, @mjbvz, @minestarks for you. Feel free to loop in other consumers/maintainers if necessary

Copy link
Member

@amcasey amcasey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but I would find it reassuring to have it tested it in VS (@minestarks?)

@sheetalkamat
Copy link
Member Author

@uniqueiniquity can you please try it out and see if this works. Would like to get this in for 3.9

@uniqueiniquity
Copy link
Contributor

@sheetalkamat trying it out now

@uniqueiniquity
Copy link
Contributor

uniqueiniquity commented Mar 19, 2020

@sheetalkamat, I've validated that compile on save still works when running with these changes in VS.
EDIT: that is, with the new flag not set.

@sheetalkamat sheetalkamat merged commit 7e07a2b into master Mar 19, 2020
@sheetalkamat sheetalkamat deleted the richCompileOnSave branch March 19, 2020 21:03
@uniqueiniquity
Copy link
Contributor

FWIW, just validated that if VS is updated to provide the new flag and handle the return type, diagnostics are returned in the scenario from #30739

@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

compileOnSaveEmitFile silently failing

5 participants