mirror of
https://github.com/ramsayleung/rspotify.git
synced 2026-04-26 07:55:55 +03:00
[GH-ISSUE #223] Implement cache token and refresh token #74
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#74
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?
Originally created by @ramsayleung on GitHub (Jul 9, 2021).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/223
Since we use explicitly individual functions to control whether to save the token into Json file:
refresh_user_token_without_cacherefresh_user_token(with cache implicitly)Honestly speaking, it's clumsy but work. We are planning to improve it, since we have discussed that making it as a feature is not a good idea, I prefer to use configuration field to control. Then @marioortizmanero already added two fields to control this behavior:
Since the skeleton has been constructed, I would like to supply the flesh to make the body complete.
@marioortizmanero commented on GitHub (Jul 9, 2021):
Check out the last comment at #4. If you want to implement the refreshing token you'll have to use a cell/mutex so that we can mutate the token without changing the signatures. I'll close that issue on favor of this.