-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix entry logic to not re-fetch data for the initial team #8349
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.
1 quick question.
// this is to keep backwards compatibility with servers that send the | ||
// threads for DM / GM regardless for every team | ||
const version = await getConfigValue(database, 'Version'); | ||
const hasThreadExclusions = isMinimumServerVersion(version, 10, 2, 0); | ||
|
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.
I can understand changes in the file /actions/remote/entry/common.ts, but what do these changes have anything to do with not re-fetching data for the initial team?
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.
The initial team selected first is already fetching its data, here we were not filtering this fetching the same data again
Cherry pick is scheduled. |
(cherry picked from commit 59a49b3)
Summary
We made some improvements to the performance of login here #8306 but there were two bugs that are fixed in this PR.
Ticket Link
N/A
Release Note