fix: Using the banner _id field as a fallback for the view.viewId field#32552
Merged
kodiakhq[bot] merged 4 commits intodevelopfrom Jun 10, 2024
Merged
fix: Using the banner _id field as a fallback for the view.viewId field#32552kodiakhq[bot] merged 4 commits intodevelopfrom
kodiakhq[bot] merged 4 commits intodevelopfrom
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 |
Contributor
|
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. |
KevLehman
reviewed
Jun 5, 2024
MarcosSpessatto
approved these changes
Jun 7, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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