fix(spotify): map Pathfinder track metadata#26
Merged
Conversation
This file contains hidden or 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
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.
I wanted to use spogo for my tool and have noticed that it doesn't show duration in json output. Fixed it with heavy codex assistance.
Summary
This fixes missing track metadata when playlist, library, and track info results come from Spotify's Pathfinder payloads.
Pathfinder does not always expose track duration as top-level
duration_msordurationMs. Depending on the endpoint, it can be nested underduration.totalMillisecondsortrackDuration.totalMilliseconds.A few other track fields also use Pathfinder-specific shapes:
contentRating.labelplayability.playableThis PR adds support for those shapes, and keeps
explicit: falsevisible in JSON when we know the value is actually present.