Skip to content

fix(site): Use correct UUID for web terminal when first opened #5404

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

Merged
merged 2 commits into from
Dec 14, 2022

Conversation

mafredri
Copy link
Member

While working on #5403 I noticed the web terminal connects with a
different UUID than what is serialized in the URL, this resulted in a
new session being opened if I refreshed the page.

The reasons seems to be that we were accessing raw DOM elements
(location.search) for navigation and omitting react-router-dom. This
resulted in a new navigation and UUID being generated after the fact.

While working on #5403 I noticed the web terminal connects with a
different UUID than what is serialized in the URL, this resulted in a
new session being opened if I refreshed the page.

The reasons seems to be that we were accessing raw DOM elements
(`location.search`) for navigation and omitting `react-router-dom`. This
resulted in a new navigation and UUID being generated after the fact.
@mafredri mafredri requested a review from a team as a code owner December 13, 2022 18:34
@mafredri mafredri requested review from code-asher and removed request for a team December 13, 2022 18:34
@mafredri mafredri self-assigned this Dec 13, 2022
@mafredri mafredri requested a review from a team December 13, 2022 18:34
Copy link
Member

@kylecarbs kylecarbs left a comment

Choose a reason for hiding this comment

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

Nice find!

@mafredri mafredri merged commit 2a4ef38 into main Dec 14, 2022
@mafredri mafredri deleted the mafredri/fix-web-terminal-uuid branch December 14, 2022 13:03
@github-actions github-actions bot locked and limited conversation to collaborators Dec 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants