-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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: Using the banner _id field as a fallback for the view.viewId field #32552
Conversation
We were having issues with the seats taken banner, which would've been undismissable because it was expecting it to have a view.viewId field But since the banner was created before we had this, it was always empty
🦋 Changeset detectedLatest commit: be9efc2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 32 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Looks like this PR is ready to merge! 🎉 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #32552 +/- ##
===========================================
- Coverage 56.41% 56.37% -0.05%
===========================================
Files 2437 2437
Lines 53773 53815 +42
Branches 11082 11097 +15
===========================================
+ Hits 30335 30336 +1
- Misses 20792 20836 +44
+ Partials 2646 2643 -3
Flags with carried forward coverage won't be shown. Click here to find out more. |
Proposed changes (including videos or screenshots)
We were having issues with the seats taken banner, which would've been un-dismissable because it was expecting it to have a view.viewId field.
But since the banner was created before we had this, it was always empty.
This banner was removed in #31047
And it got into the 6.5.0 release onwards, so whenever someone hadn't dismissed the seatsTaken banner and upgraded their workspace, it would now be un-dismissable and would show a toast with the error 'invalid banner'
Issue(s)
Steps to test or reproduce
(I've had a few issues trying to run this test, my MongoDB would fail to start properly on 6.4.9. To solve this issue, I've deleted the contents of .meteor/local, which did the trick for me :) )
This should actually close the banner and add it to the dismissed banners collection inside MongoDB
Further comments
I could've just added a new migration that would put the value of _id inside the view.viewId field, but since we already have adaptations to have legacy banners I don't think we should add a new migration just for this :P
JIRA Task: https://rocketchat.atlassian.net/browse/SUP-437