Feature: Dynamic storage target

[stevehaneytrailblazer]

I'm submitting a...

[x] Other... Please describe:

Current behavior

Currently you have to decide overall what the storage pattern will be (whether memory, local storage, custom, etc...)

Possible behavior?

I was curious if anyone has asked for the ability to pass a storage parameter in the withContext so you could declare a storage target specific to different API calls.

The reason I bring this up is that there might be some non sensitive API calls that return application configuration that would be a good candidate for localStorage where I get the benefit of multiple browser tabs sharing that information. Whereas I might have some other data I'd like to cache in the browser but just inMemory that I wouldn't want to leave in localStorage.

Perhaps the answer would be to write a custom storage provider but I was just curious if anyone had asked for something like this or if there's a strong reason why its very difficult or not a good idea.

Great library btw. Thanks for your time!

[NetanelBasal]

You're welcome to submit a PR with this feature.