mirror of
https://github.com/ramsayleung/rspotify.git
synced 2026-04-26 07:55:55 +03:00
[GH-ISSUE #135] Consider making the cache file a feature #48
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#48
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 @marioortizmanero on GitHub (Oct 10, 2020).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/135
The cache file feature is something I'm not sure how I feel about. While it's definitely useful, I'm not sure if it should be the default behaviour. It could be moved into a feature, which when activated, would use the cache file anywhere possible. Or instead of having
do_somethinganddo_something_without_cache, it could bedo_somethinganddo_something_with_cache.What do you think? I need some opinions on this. I don't actually plan on changing anything but I want to propose any breaking changes before the next release.
@ramsayleung commented on GitHub (Oct 11, 2020):
Yes, I think it's more proper to have a switch to control how does it work. My original thought was using
cache_pathas a trigger, as what I commented in #129:Now, probably it's more suitable to make it as a feature, switching on compile time instead of runtime, as what you suggests.
@ramsayleung commented on GitHub (Oct 24, 2020):
Any other proposals? I am gonna to start to work on this feature on this weekend as what @marioortizmanero suggests, makes cache file as a new feature.
@marioortizmanero commented on GitHub (Oct 24, 2020):
Can you cross off more things from the meta issue before this? I would wait a bit more before this, let's see if anyone opposes the idea.
@ramsayleung commented on GitHub (Oct 24, 2020):
Sure! We could leave this issue alone for a while.
@marioortizmanero commented on GitHub (Dec 28, 2020):
This has been inactive for a while and noone has left their opinion so I would say we can introduce the
cache-filefeature. Should it be activated by default?Also, do you still want to work on it @ramsayleung?
@ramsayleung commented on GitHub (Dec 30, 2020):
I think it would be good to active this feature by default, just makes
rspotifywork as before.Not yet, I am working on this issue: https://github.com/ramsayleung/rspotify/issues/163, I would like to work on this feature after merging the PR of #163, and we could say we have crossed off most of TODO items in #127