mirror of
https://github.com/ramsayleung/rspotify.git
synced 2026-04-26 07:55:55 +03:00
[PR #139] [MERGED] PlayHistory returns FullTrack despite Spotify documentation #264
Labels
No labels
Stale
bug
discussion
enhancement
good first issue
good first issue
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rspotify#264
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/ramsayleung/rspotify/pull/139
Author: @aramperes
Created: 10/15/2020
Status: ✅ Merged
Merged: 10/17/2020
Merged by: @ramsayleung
Base:
master← Head:full-track-playhistory📝 Commits (2)
9456955PlayHistory returns FullTrack despite Spotify documentationbfb4440Update CHANGELOG.md📊 Changes
2 files changed (+2 additions, -2 deletions)
View changed files
📝
CHANGELOG.md(+1 -0)📝
src/model/playing.rs(+1 -2)📄 Description
Despite what the Spotify documentation specifies, the
play history objecthas aFullTracktrack field. This can be seen by using the endpoint and noticing that all fields are returned in the track object (notice the album, popularity, and other fields):🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.