-
Notifications
You must be signed in to change notification settings - Fork 277
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
add join notifier support #5241
add join notifier support #5241
Conversation
ouldsmobile
commented
Sep 20, 2018
•
edited
Loading
edited
- PR is based on the DEVELOP branch
- Don't send big changes all at once. Split up big PRs into multiple smaller PRs that are easier to manage and review
- Read the contribution guide
fixed |
fixed |
Please fix all the issues pointed out by the travis build. Ow and the PR is still subjected to a proper review. I just pointed out the obvious issues. |
Thanks for the help. Think I got it sorted now. As you can probably guess I am quite new to github and contributing code. Just wanted to contribute something to the project. Hope it helps! |
medusa/notifiers/join.py
Outdated
@@ -1,4 +1,8 @@ | |||
# coding=utf-8 | |||
# Author: Kevin Ould email: ouldsmobile1@gmail.com | |||
# Thanks to the contributors of the other notifier providers | |||
# for inspiration and a base to start from |
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.
Extra notes are unneeded.
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.
removed
Ive decided that this will have to wait on #4913 Which means youll have to rewrite part of your code in vue.js. |
Ok, thanks for the update. So, once 4913 is merged I will update vue.js to work with new build. Will I be automatically notified when 4913 is merged or should I just keep checking on things? Sorry, again new to contributing to github. Still learning. |
Will take at least another week. So you can check in next week. |
You can rebase on develop now and continu |
DeepCode analyzed this pull request. Click to see more details. |
@@ -1518,14 +1518,14 @@ window.app = new Vue({ | |||
<div class="col-xs-12 col-md-10"> | |||
<fieldset class="component-group-list"> | |||
<!-- All form components here for join client --> | |||
<config-toggle-slider :checked="notifiers.join.enabled" label="Enable" id="use_join" :explanations="['Send join notifications?']" @change="save()" @update="notifiers.join.enabled = $event"></config-toggle-slider> | |||
<config-toggle-slider v-model="notifiers.join.enabled" label="Enable" id="use_join" :explanations="['Send join notifications?']" @change="save()" @update="notifiers.join.enabled = $event"></config-toggle-slider> |
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.
You can also remove the @update now
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.
Done!
You need to run yarn dev, to fix the build |
… unneeded line in config_notifications.mako
DeepCode analyzed this pull request. |
Disregard, think I have it sorted now. Will update shortly. |
Any idea why the frontend travis test keeps failing? All I can gather is the build-themes-check failed but not sure why? Seems to run fine locally with no errors. |
Try removing node_modules |
Ok, ran that locally in root of build. Here is the tail: `Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo&)’} [-Wcast-function-type] make: Leaving directory '/home/kevin/Medusa/node_modules/protagonist/build' gyp ERR! build error gyp ERR! stack Error: gyp ERR! stack at ChildProcess.onExit (/home/kevin/.config/yarn/global/node_modules/node- gyp ERR! stack at ChildProcess.emit (events.js:182:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12) gyp ERR! System Linux 4.18.16-arch1-1-ARCH gyp ERR! command "/usr/bin/node" "/home/kevin/.yarn/bin/node-gyp" "rebuild" gyp ERR! cwd /home/kevin/Medusa/node_modules/protagonist gyp ERR! node -v v11.0.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok" info This module is OPTIONAL, you can safely ignore this error $ yarn run lint yarn run v1.12.1 $ node ./themes-default/helper.js lint Starting lint of /home/kevin/Medusa/themes-default/slim $ /home/kevin/Medusa/themes-default/slim/node_modules/.bin/xo Done in 1.71s. Done in 90.59s. |
You need to run that from /home/kevin/Medusa/themes-default/slim |
Ah ok. Seemed to run without error. Here is the output from that: `yarn install v1.12.1 warning package.json: No license field warning slim@0.1.0: No license field [1/4] Resolving packages... [2/4] Fetching packages... info fsevents@1.2.4: The platform "linux" is incompatible with this module. info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from [4/4] Building fresh packages... $ yarn run lint yarn run v1.12.1 warning package.json: No license field $ xo Done in 1.46s. Done in 9.03s. |
And now run from the same dir: |
Thanks for the help! Passing checks now. |
I noticed the schemes for notify_snatch, notify_download and notify_subtitle_download have changed since I originally wrote my join.py. notify_snatch has been taken care of with pr #5584 but the other two need to be fixed as well. I have edited and fixed in my repo. What is the proper way to merge the changes into develop now? Make another pull request? Or can you just make the necessary changes? I want to do things correctly. |