LocalForage Config Properties Hard-Coded Preventing Data Separation Across Stores about forerunnerdb HOT 8 CLOSED

So the way we've decided to do this is:

var fdb = new ForerunnerDB('myStoreName');

You name your forerunnerdb instance first, then all other sub-instances are namespaced. Update coming very soon.

from forerunnerdb.

Can you include the name property too (currently ForerunnerDB) as this is the true database app separation from localforage's perspective.

from forerunnerdb.

Or use the name property rather than the storeName if you prefer only one config property. Name is more important than storeName from an app separation concern.

from forerunnerdb.

I had envisaged using the instance name (passed in ForerunnerDB() instantiation) as the "name" property and the DB name as the "storeName" property.

Would this work for your use case?

from forerunnerdb.

Perfect.

from forerunnerdb.

:) 👍 fantastic.

from forerunnerdb.

OK could you give that a go? I've set up tests (they are passing) and merged changes. New version 1.3.54.

I couldn't use the db name as the storeName parameter because chrome complained. You can test on Chrome yourself by editing the JS code in realtime and providing any other string instead of "FDB" and it will fail to get the store. I don't know why it is happening but anyway, this should be enough to satisfy your requirement hopefully since now you can namespace the whole instance for different app customers while keeping the DB name the same if you want to and the persisted data will be unique.

Let me know if it is doing what you need.

from forerunnerdb.

Works great. Thanks for a quick resolution.

from forerunnerdb.