Transfer lock to next oldest session when disconnecting from the builder #10789
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.
Description
This PR adds a new feature to collaboration, so that whenever the "primary" user disconnects (the person who can edit screens and automations), this ability is automatically transferred to the user who has also been editing the same app the longest.
The prevents the need to either refresh your browser or exit the app and enter it again in order to be able to edit screens.
The user who gets control will get a notification letting them know they're able to edit screens and automations now, and their builder will automatically update itself.
This PR also slightly updates the websocket API to ensure that all payloads are wrapped in objects.
Addresses:
See it in action here:
Screen.Recording.2023-06-05.at.13.47.45.mov