MTG2000
commented
1 year ago Actually, after thinking about it more... I think that having a separate cache for each topic might be a good idea.
And that's for several reasons:
- When you enter "Write a story" page in a specific topic, then this 'write-story' page acts like it belongs to this topic community, it's not the same default global community. So when you think of it this way, it makes sense that each community's editor has its own cache.
- The local cache is NOT a replacement for Drafts. Local cache is primarily for the cases where the user exits/reloads/loses-internet-connection while writing his story. It's not meant for long-term storage. For long-term storage, drafts are what should be used.
- I was a little concerned regarding the browser's localStorage limits, but after looking it up, I think it would be fine.
So following this approach, our cache logic would look something like this simplified diagram:
johnsBeharry
Originally, we only had 2 ways for the user to enter the "write-story" page:
So in the case of writing a new story, we were using
localStorageto cache the values of the inputs fields, so that if the user reloads the page, the inputs will still have the values they had.However, lately, we've added a new way to enter to the write-story page, and that's from the topics page. Where the Tag input field will be pre-filled with the tag that the user were on.
But what will happen if the user has already had some cached data in the localStorage? Should we delete that data?? Ignore that data??
And when he starts writing his new story, should we write over the cached values in the localStorage? Or if there is some data there but it's been ignored, should we NOT write to the localStorage?
Johns suggested a solution where we keep a local cache FOR EACH different topic, and one cache for the NO-TOPIC case. This could solve some aspects of the problem, but it brings its own challenges with it too. (Primarily that we will need to add a new components to the "write-story" page that shows all the cached different stories with the ability to "restore them back in". But this feels very close to Drafts, so maybe we should think of something a little different)
I think we should look into other websites who have scenarios similar to ours, & see how they are handling it.