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
Just a suggestion: If one uses definition caching, the cache grows rapidly, even after the fix not to double-cache. I don’t think it’s wise to keep all this together with the plugin settings in data.json.
Instead, I propose to use a separate cache.json, which would also make the deleting of the cache much easier.
The data file currently uses a lot of space because it is "pretty" JSON. I don’t think users will ever manually edit it, so I also propose to use something like JSON.stringify() to make it more compact and faster loading.
How do you feel about that?
The text was updated successfully, but these errors were encountered:
Moonbase59
changed the title
Suggestion: Use a separate file for the cached definitions
Suggestion: Use separate file for the cache, reduce size
Jul 22, 2021
Just a suggestion: If one uses definition caching, the cache grows rapidly, even after the fix not to double-cache. I don’t think it’s wise to keep all this together with the plugin settings in
data.json
.Instead, I propose to use a separate
cache.json
, which would also make the deleting of the cache much easier.The data file currently uses a lot of space because it is "pretty" JSON. I don’t think users will ever manually edit it, so I also propose to use something like
JSON.stringify()
to make it more compact and faster loading.How do you feel about that?
The text was updated successfully, but these errors were encountered: