[GH-ISSUE #450] Incorrect url in OAuthClient documentation #149

Closed
opened 2026-02-27 20:23:24 +03:00 by kerem · 1 comment
Owner

Originally created by @Arya-LL on GitHub (Jan 2, 2024).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/450

Describe the bug
The documentation for the OAuthClient trait has the wrong url for the reference link (line 960, file src/clients/oauth.rs)

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'fn current_playing under rspotify::clients::OAuthClient in rspotify's documentation'
  2. Click on 'Reference'

Expected behavior
Expect to find https://developer.spotify.com/documentation/web-api/reference/get-the-users-currently-playing-track

Log/Output data
Redirected to https://developer.spotify.com/documentation/web-api/reference/get-recently-played

Additional context
I am new to GitHub and contributing to open-source projects, I apologize if I addressed the issue incorrectly. Thank you for the amazing project!

Originally created by @Arya-LL on GitHub (Jan 2, 2024). Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/450 **Describe the bug** The documentation for the OAuthClient trait has the wrong url for the reference link (line 960, file src/clients/oauth.rs) **To Reproduce** Steps to reproduce the behavior: 1. Go to 'fn current_playing under rspotify::clients::OAuthClient in rspotify's documentation' 2. Click on 'Reference' **Expected behavior** Expect to find https://developer.spotify.com/documentation/web-api/reference/get-the-users-currently-playing-track **Log/Output data** Redirected to https://developer.spotify.com/documentation/web-api/reference/get-recently-played **Additional context** I am new to GitHub and contributing to open-source projects, I apologize if I addressed the issue incorrectly. Thank you for the amazing project!
kerem 2026-02-27 20:23:24 +03:00
Author
Owner

@ramsayleung commented on GitHub (Jan 3, 2024):

This problem has been fixed in this PR :)

<!-- gh-comment-id:1874861079 --> @ramsayleung commented on GitHub (Jan 3, 2024): This problem has been fixed in this [PR](https://github.com/ramsayleung/rspotify/pull/451) :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/rspotify#149
No description provided.