Namespaced persistence

[rivertam]

• has-reproduction
• feature
• docs
• blocking
• good first issue

Hi! ^ Hope I did that right. I'm using web, so I'll use web terminology/concepts and hope it translates.

I'm considering using this to persist some data. However, I'd like to keep separate caches to keep the data separate. I'm not sure if this is a great architectural idea overall, but it's striking me as clean at the moment. I also might want to keep stuff in local storage that isn't from apollo cache. In order to persist it, I think the library will need to basically namespace it as separate keys in storage. Is this library capable of doing such a thing? And, if so, how?

Thanks!

[rivertam]

Oh, I didn't read clearly enough. I think key should work for my needs. Will reopen if it turns into an issue. Sorry for creating an unnecessary issue!