Helm integration #52
Open
Helm integration #52
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Will make a issue for this soon
- clean up track search as well
- Add info of tracks loaded for a playlist
- Also fix bug from server side regarding empty song object
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a change that involves extending the current features of the package to enable a helm frontend through a flag variable called
spotify-helm-integrationand also partially addresses issue #24. This change shouldn't affect old behaviour but please notify me if it does.I've also added Spotify's queue API which in my opinion seems to tie in well as actions within helm buffers.
If more features are added to either this package or Spotify's Web API then I may be able to help out if I have free time otherwise this should be a good start.