-
Notifications
You must be signed in to change notification settings - Fork 366
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
Abstract client #39
Abstract client #39
Conversation
… to OSX binaries aka afplay + say)
…288) and add a client exclusively for testing.
This looks pretty good. There's been a few changes since this Pull came in; would you mind merging master in and resolving any conflicts? A few more bits of feedback I'd like to tackle before this gets merged properly:
Okay maybe that's it. Looks pretty sharp. |
Conflicts: bin/setup config/play.example.yml
So, I have some concerns with testing of clients. I'd like to make TestClient more realistic and then provide a way to compare the operation of TestClient with an arbitrary client implementation which should help client maintainers keep their code quality up. But thats another day. Today :D |
@@ -104,6 +117,7 @@ sed -i '' "s/__OAUTH_KEY__/$client_id/" config/play.yml | |||
sed -i '' "s/__OAUTH_SECRET__/$client_secret/" config/play.yml | |||
sed -i '' "s/__USER__/$user/" config/play.yml | |||
sed -i '' "s/__PASSWORD__/$password/" config/play.yml | |||
sed -i '' "s/__CLIENT__/$client/" config/play/yml |
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 think you meant config/play.yml
and not config/play/yml
blurgh. Thanks for the catch. |
We take Client and make it a class to be inherited by real clients. The setup script will select afplay or mpg123 based on what it can find, we also add support for mpc (the mpd client) since that is what we use at our workplace.