Skip to content
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

Merged
merged 45 commits into from
Nov 3, 2018

Conversation

ouldsmobile
Copy link
Contributor

@ouldsmobile ouldsmobile commented Sep 20, 2018

  • 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

@ouldsmobile
Copy link
Contributor Author

Copy/paste

fixed

@ouldsmobile
Copy link
Contributor Author

Why did you change this to double quotes? We use single for strings.

fixed

@p0psicles
Copy link
Contributor

p0psicles commented Sep 20, 2018

Please fix all the issues pointed out by the travis build.
Frontend: xo/eslint js linting. Don't forget to run yarn dev
backend: pep
dredd: probably have to check apiv2 and dredd/api-description.yml

Ow and the PR is still subjected to a proper review. I just pointed out the obvious issues.

@ouldsmobile
Copy link
Contributor Author

Please fix all the issues pointed out by the travis build.
Frontend: xo/eslint js linting. Don't forget to run yarn dev
backend: pep
dredd: probably have to check apiv2 and dredd/api-description.yml

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!

@medariox medariox added Needs review Needs testing Requires testing to make sure it's working as intended labels Sep 21, 2018
@@ -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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extra notes are unneeded.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@p0psicles
Copy link
Contributor

Ive decided that this will have to wait on #4913

Which means youll have to rewrite part of your code in vue.js.

@ouldsmobile
Copy link
Contributor Author

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.

@p0psicles
Copy link
Contributor

Will take at least another week. So you can check in next week.

@OmgImAlexis OmgImAlexis added this to the 0.2.12 milestone Sep 29, 2018
@p0psicles
Copy link
Contributor

You can rebase on develop now and continu

@ghost
Copy link

ghost commented Oct 31, 2018

DeepCode analyzed this pull request.
There are 2 new info reports.

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>
Copy link
Contributor

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

@p0psicles
Copy link
Contributor

You need to run yarn dev, to fix the build

medusa/notifiers/join.py Outdated Show resolved Hide resolved
themes-default/slim/src/store/modules/notifiers.js Outdated Show resolved Hide resolved
themes-default/slim/views/config_notifications.mako Outdated Show resolved Hide resolved
@ghost
Copy link

ghost commented Nov 1, 2018

DeepCode analyzed this pull request.
There are no new issues.

@ouldsmobile
Copy link
Contributor Author

ouldsmobile commented Nov 2, 2018

Disregard, think I have it sorted now. Will update shortly.

@ouldsmobile
Copy link
Contributor Author

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.

@p0psicles
Copy link
Contributor

Try removing node_modules
Run: yarn install --prod false --check-files

@ouldsmobile
Copy link
Contributor Author

ouldsmobile commented Nov 2, 2018

Try removing node_modules
Run: yarn install --prod false --check-files

Ok, ran that locally in root of build. Here is the tail:

`Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo&)’} [-Wcast-function-type]
make: *** [protagonist.target.mk:155: Release/obj.target/protagonist/src/parse_async.o] Error 1

make: Leaving directory '/home/kevin/Medusa/node_modules/protagonist/build'

gyp ERR! build error

gyp ERR! stack Error: make failed with exit code: 2

gyp ERR! stack at ChildProcess.onExit (/home/kevin/.config/yarn/global/node_modules/node-
gyp/lib/build.js:262:23)

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.
`

@p0psicles
Copy link
Contributor

You need to run that from /home/kevin/Medusa/themes-default/slim

@ouldsmobile
Copy link
Contributor Author

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
installation.
[3/4] Linking dependencies...

[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.
`

@p0psicles
Copy link
Contributor

And now run from the same dir: yarn dev

@ouldsmobile
Copy link
Contributor Author

And now run from the same dir: yarn dev

Thanks for the help! Passing checks now.

@p0psicles p0psicles merged commit 676b11e into pymedusa:develop Nov 3, 2018
@ouldsmobile
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs review Needs testing Requires testing to make sure it's working as intended
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants