-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
MM-28733 : Admin Advisor v2 #15515
MM-28733 : Admin Advisor v2 #15515
Conversation
Failed running enterprise tests. @mattermost/core-build-engineers have been notified. Error: |
Failed running enterprise tests. @mattermost/core-build-engineers have been notified. Error: |
@catalintomai since the messages are still not ready and finalized by @esadur, I will only be able to test the PRs once they are finalised. |
@jasonblais Catalin has just added a placeholder for messages. The actual messages are still not finalized by Eric. |
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.
Some other general comments (not specific to this PR) but maybe tickets can be made for them?
I noticed that BuildEnterpriseReady
was a string declared four years ago and I think it's kinda weird how a boolean variable was initialized a string (maybe a reason for this that I'm not sure) but I feel like this should be a boolean and not a string since throughout the code we have many places checking to see if the value is 'true'.
I think maybe not changing the variable type to boolean but making some sort of function like "func BuildEnterpriseReadyAsBoolean" where then we can just do "model.BuildEnterpriseReadAsBoolean" rather than always needing to do a "model.BuildEnterpriseReady == 'true'". Just my 2 cents and I feel that it could help alleviate the constant "== true" part.
Otherwise all looks good! Thanks
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.
I guess my last comment would be using squirrel instead of plain sql due to our move to using squirrel. Otheriwse, with respect to above comments, everything else looks good.
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.
Tested the updated PR along with it's dependent PRs and all the issues are now fixed and are working fine. Approving the PR.
@mkraft Kind note to review for v5.28. |
Cherry pick is scheduled. |
(cherry picked from commit f74b86a)
Summary
Admin Advisor v2.
Ticket Link
https://mattermost.atlassian.net/browse/MM-28733
Related Pull Requests
webapp: mattermost/mattermost-webapp#6461
API: mattermost/mattermost-api-reference#574