mirror of
https://github.com/ramsayleung/rspotify.git
synced 2026-04-26 07:55:55 +03:00
[PR #42] [MERGED] get_token processing can be done in two parts #201
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#201
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/42
Author: @braincow
Created: 5/29/2019
Status: ✅ Merged
Merged: 5/30/2019
Merged by: @ramsayleung
Base:
master← Head:two_part_token_request📝 Commits (2)
0492408get_token processing can be done in two parts4d1bec7Merge branch 'master' into two_part_token_request📊 Changes
1 file changed (+19 additions, -13 deletions)
View changed files
📝
src/spotify/util.rs(+19 -13)📄 Description
This patch separates get_token functionality into two different functions while still maintaining legacy compatibility where user is queried on the command line for return URL address.
Separating the behavior allows handling request and verification of received token in code. For example: I am working on a small app that spawns a simple http server to localhost to wait for users browser to return back from Spotify website. Thus user never needs to enter the values themselves to console.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.