Fixed audio_features API wrapper function return structure #653
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
|
I have changed the base from |
stephanebruckert
added a commit
that referenced
this pull request
Dec 26, 2022
Co-authored-by: Stéphane Bruckert <stephane.bruckert@gmail.com>
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.
Currently the function wrapping the
audio_features(querying the audio features for multiple tracks) unwraps the single-entry of the JSON object returned by the Spotify API endpoint it wraps. Currently, other functions similar endpoints, querying multiple tracks, artists, albums, etc, do not unwrap the JSON response. This change aims to conform the audio_features function's return type. See this comment from a similar pull request for context.