-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Only connect to ServerConnections once #6150
base: master
Are you sure you want to change the base?
Conversation
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.
ESLint doesn't pass. Please fix all ESLint issues.
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.
ESLint doesn't pass. Please fix all ESLint issues.
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.
ESLint doesn't pass. Please fix all ESLint issues.
1428d79
to
32e078b
Compare
32e078b
to
557eea5
Compare
557eea5
to
d580429
Compare
Quality Gate passedIssues Measures |
There is an issue where if you try to login after refreshing the login page it won't redirect you (this existed prior to this PR, even in 10.9), so might as well fix it here. |
Cloudflare Pages deployment
|
Currently, the client will send a request to
ServerConnections.connect
every time we switch pages. With this, the behaviour should now be the same as prior to app routing being removed.Changes
Change it so that we only connect to ServerConnections once with each session, reducing unnecessary calls to
/System/Info/Public
with each navigation.Issues
Fixes #6143