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 nav bar performance issue #7967
Fix nav bar performance issue #7967
Conversation
@@ -1,17 +1,17 @@ | |||
import React, { PureComponent } from 'react'; | |||
import React, { } from 'react'; |
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.
Just out of curiosity, why sometimes you use named import and sometimes you use React.
?
|
||
const PUBLIC_CONFIG = Meteor.settings.public; | ||
|
||
const ROLE_MODERATOR = Meteor.settings.public.user.role_moderator; |
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.
PUBLIC_CONFIG.user.role_moderator
maybe?
bigbluebutton-html5/imports/ui/components/nav-bar/recording-indicator/component.jsx
Outdated
Show resolved
Hide resolved
…dicator/component.jsx Co-Authored-By: Chad Pilkey <capilkey@gmail.com>
…404/bigbluebutton into nav-bar-performance-issue
We don't clear |
bigbluebutton-html5/imports/ui/components/nav-bar/recording-indicator/component.jsx
Outdated
Show resolved
Hide resolved
bigbluebutton-html5/imports/ui/components/nav-bar/recording-indicator/component.jsx
Outdated
Show resolved
Hide resolved
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.
Works great!
This PR inted to fix performance issues in nav bar and move the recordProp field from the meeting collection to own collection in mongoDB.
To test it I advice to use the npm package why did you update this package list all updates and it causes.