This repository was archived by the owner on Jul 18, 2022. It is now read-only.
[Live Share] Allow developers to specify a profile to use when hosting Live Share sessions #4
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.
This PR introduces the notion of a "Live Share profile", which enables developers to automatically switch between profiles when they start a Live Share session. When you're hosting a Live Share session, your editor settings impact all guests in the session (but not your personalization settings!), and therefore, it could be valuable to have a profile that you use for collaboration, which is more amenable to your peers if you collaborate frequently (e.g. turning off auto-save/format on save/etc).
This could also allow activating extensions only when a Live Share session is active, which could be valuable when you want to use extensions that only contribute to Live Share (e.g. whiteboard).
Below is a demo gif that shows the
files.autoSave
setting being toggled automatically when starting and stopping a Live Share session: