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
Revive Beatport plugin with support for OAuth API (#1989) #2067
Conversation
Yay! Fantastic -- this looks great after a quick review. For the documentation, shall we revive the old documentation file too and add notes about the new OAuth workflow? And not that it's urgent, but some of the methods in |
Yes, that's the most sensible way to go, since the OAuth thing is the only thing that has changed since the removal. I just added the old documentation file with a new paragraph on the OAuth workflow.
Done! :-) |
Revive Beatport plugin with support for OAuth API (#1989)
Wahoo! ✨ That was fast! And the new text in the docs looks great. I'm happy we get to have a Beatport plugin again! 🚀 |
I'm up to date with the latest master branch, but am still getting |
Hmm, that's odd -- maybe you need to uninstall and reinstall? Things seem to work fine here. |
That's peculiar. What's the output from |
@sampsyo I actually did just uninstall & re-install because I was getting that error initially, but got it again after a clean install. @jackwilsdon |
@sampsyo what does your config file look like as far as options go? |
This is the whole config file: plugins: beatport |
@sampsyo @jackwilsdon scratch that - I figured it out. I re-installed to a different folder and forgot to update the plugin path in |
@sampsyo so since there's no args to pass with it then does it just fetch all available metadata that beatport has? |
Yes. |
I just ran it, go the string in the browser but then got this: |
Do you think you could open a new issue with all of the necessary information @BrianRoach? |
@jackwilsdon will do. |
This is a bad naming confusion on my part, I had the client stored under |
@jbaiter ah, no worries. thanks! |
I am so glad this has finally made a comeback - thanks @jbaiter |
This restores the previously removed Beatport plugin, this time around with support for their API version 3, which requires OAuth authentication with all endpoints.
The process of obtaining the authentication token and secret is modeled after the way the
discogs
plugin handles this, i.e. the user is asked to visit a website, enter her credentials and then paste the displayed string into the terminal. The plugin then extracts the token/secret and stores it in a file in the configuration directory.I have not yet tested the integration with beets, so I would welcome any curious testers to try it out.