You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should change the default cache location the next time we release a breaking update. I think the earliest we can do that is with version 2.0 (which is a far ways off, not even planned).
Currently the path used is the temporary directory appended with a path component that is very specific.
@8W9aG we could probably include a migrator, yeah. I guess we could try to move the old directory to the new name. Making sure we don’t overwrite anything though.
If it fails we could write a small .we-tried-to-migrate-but-if-failed-so-let-us-not-try-again file in the old directory. So we don’t get stuck in some bad loop where we try to migrate every time the app launches.
We should change the default cache location the next time we release a breaking update. I think the earliest we can do that is with version 2.0 (which is a far ways off, not even planned).
Currently the path used is the temporary directory appended with a path component that is very specific.
(
SPTPersistentCacheOptions.m#L51
)It would be better to set it to a more generically named path, such as:
The text was updated successfully, but these errors were encountered: