-
Notifications
You must be signed in to change notification settings - Fork 13k
chore: Stop using Livechat_Room_Count setting
#35017
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
Conversation
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #35017 +/- ##
===========================================
- Coverage 59.17% 59.17% -0.01%
===========================================
Files 2822 2822
Lines 68118 68117 -1
Branches 15145 15145
===========================================
- Hits 40312 40311 -1
Misses 24975 24975
Partials 2831 2831
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
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 to create a task to create a migration to a major version? So we can remove the setting?
|
Yup, I'm creating the other task to remove the setting. This one will just stop using it (as we're updating it for no reason everytime a new Omni room is created) |
Livechat_Room_Count settingLivechat_Room_Count setting
Proposed changes (including videos or screenshots)
Setting was not being used anywhere, we can safely remove.
Thought on using it for metrics, but it's generally easier a count on the collection with the
estimatedDocumentCountwe have right now than to keep track of this value.Issue(s)
https://rocketchat.atlassian.net/browse/CORE-930
Steps to test or reproduce
Further comments
Ok, maybe we're not removing here entirely, but the point is to stop using it. There's another task for the migration to remove it.