-
Notifications
You must be signed in to change notification settings - Fork 14
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
[GH-54] sync with latest mattermost-plugin-starter-template #68
Conversation
Codecov Report
@@ Coverage Diff @@
## master #68 +/- ##
==========================================
+ Coverage 29.48% 30.08% +0.59%
==========================================
Files 8 9 +1
Lines 234 236 +2
==========================================
+ Hits 69 71 +2
Misses 153 153
Partials 12 12
Continue to review full report at Codecov.
|
5e7c446
to
832471c
Compare
golangci-lint fixes make check-style fixes broken test fixes
832471c
to
321dfe9
Compare
I quite like having colorized terminal output and although I am pulling this OUT of the Makefile, what do you guys think about adding this color highlighting to our Makefile :) |
@jfrerich Do you mind going in detail with your process how you performed this sync? |
@mickmister, I followed the steps found inside #69. It would be great to have this PR for doing this. I will have to get back to that ticket and see if I can repro much of the changes needed for the syncing in this PR. |
@jfrerich Any reason we can't use the plugin repo sync tool? Here's my test drive of using it mattermost-community/mattermost-plugin-todo#103 , including the plan.yml I used to sync. You can adjust the original plan.yml as you see fit. |
Nice. I hadn't seen the sync tool in use! I'll have to test it out also and see how it reacts against my changes. |
…update package.json files.\n add eslint exception rule to test so it passes eslint
So, I did find some changes that I missed. I also have quite a few differences with
|
ok! There were quite a few commits needed after addressing those latest comments (syncing webpack, package.json, socket API), but this is ready for re-review |
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.
LGMT 👍
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.
Nothing blocking but I'm curious about some of the string changes.
server/service/get_subscription.go
Outdated
@@ -8,7 +8,7 @@ import ( | |||
"github.com/mattermost/mattermost-plugin-confluence/server/serializer" | |||
) | |||
|
|||
const generalError = "Some error occurred. Please try again after sometime." | |||
const generalError = "some error occurred. Please try again after sometime" |
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 was this changed to lowercase? Same with other similar string changes.
Also a grammar suggestion:
const generalError = "some error occurred. Please try again after sometime" | |
const generalError = "some error occurred. Please try again after some time" |
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.
What about the grammar suggestions regarding capitalization? Is there a reason why this was made lowercase?
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.
It was a linting error, so I changed it
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.
What was the linting error? It seems incorrect to me to display an error message that begins with a lowercase letter, when it is meant to be a sentence. Definitely something we want to fix in our lint settings rather than doing it this way 2/5
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.
Here is the explanation for the linting error. https://github.com/golang/go/wiki/CodeReviewComments#error-strings
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.
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 sort of disagree with it, if you're trying to have full sentences in an error message. But I think they are advising to not have full sentences in the error description portion of a log for example.
webapp/src/client/client.js
Outdated
this.baseUrl = url.protocol + '//' + url.host; | ||
this.pluginUrl = this.baseUrl + '/plugins/' + Constants.PLUGIN_NAME; | ||
this.apiUrl = this.baseUrl + '/api/v4'; | ||
this.pluginApiUrl = this.pluginUrl + '/api/v1'; |
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.
Why were these changed to using the +
syntax?
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.
Leaving these with the ${url.protocol}
causes eslint to fail. I don't like the change, but made it to move forward with the PR
webapp/src/constants/action_types.js
Outdated
RECEIVED_SUBSCRIPTION: `${PLUGIN_NAME}_received_subscription`, | ||
OPEN_SUBSCRIPTION_MODAL: PLUGIN_NAME + '_open_subscription_modal', | ||
CLOSE_SUBSCRIPTION_MODAL: PLUGIN_NAME + '_close_subscription_modal', | ||
RECEIVED_SUBSCRIPTION: PLUGIN_NAME + '_received_subscription', |
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.
Is something in the eslint config suggesting this change?
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.
Unfortunately yes this caused eslint to fail.
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.
What rules caused it to fail? The config should be updated to support the better syntax
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.
Apparently this is a bug eslint/eslint#13248
use id, from webapp/src/manifest.js, instead of hardcoded PLUGIN_NAME from webapp/src/constants/manifest
@mickmister I went ahead and addressed some of your comments in another commit. Can you please re-review? |
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 and Passed
- Build and deployed
- Briefly regression tested
- No issues found no further functional testing needed for this PR
LGTM!
Release testing will take place on next version bump.
Summary
Syncs with latest mattermost-plugin-starter-template
Ticket Link
Fixes:
#54
#69