-
Notifications
You must be signed in to change notification settings - Fork 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
Keep on sync the current team id with mattermost since the beginning #3499
Keep on sync the current team id with mattermost since the beginning #3499
Conversation
store.subscribe(() => { | ||
const currentTeamID = store.getState().teams.currentId | ||
if (currentTeamID && currentTeamID !== fbPrevTeamID) { | ||
if (fbPrevTeamID && window.location.pathname.startsWith(windowAny.frontendBaseURL || '')) { |
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.
Do we need this empty if check?
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.
🤦 clearly that isn't needed.
…on-sync-with-mattermost
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.
LGTM 👍
Cherry pick is scheduled. |
…attermost-community#3499) * Keep on sync the current team id with mattermost since the beginning * Removing unneeded code (cherry picked from commit 08dd39d)
Summary
The selected team is handled by the mattermost-webapp code using the mattermost
store data, in this case the current team.
This PR forces to update the mattermost Channels current team id whenever it
changes on Boards.
Ticket Link
Fixes #3458