mirror of
https://github.com/ramsayleung/rspotify.git
synced 2026-04-25 23:45:52 +03:00
[PR #406] [CLOSED] Add token fetch callback #438
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#438
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/406
Author: @PaulOlteanu
Created: 4/27/2023
Status: ❌ Closed
Base:
master← Head:add-token-fetch-callback📝 Commits (2)
c483de6Initial implementation of token callback88711ebHandle implementation of Debug for token callback📊 Changes
6 files changed (+49 additions, -5 deletions)
View changed files
📝
Cargo.toml(+1 -1)📝
src/auth_code.rs(+10 -1)📝
src/auth_code_pkce.rs(+10 -1)📝
src/client_creds.rs(+10 -1)📝
src/clients/base.rs(+17 -0)📝
src/clients/mod.rs(+1 -1)📄 Description
Description
Please include a summary of the change and which issue is fixed
Motivation and Context
#400
Please also include relevant motivation and context.
Dependencies
List any dependencies that are required for this change.
Type of change
Please delete options that are not relevant.
How has this been tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Please also list any relevant details for your test configuration
Is this change properly documented?
Please make sure you've properly documented the changes you're making.
Don't forget to add an entry to the CHANGELOG if necessary (new features, breaking changes, relevant internal improvements).
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.