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
Currently, even if you're only getting a single kv pair, if that lookup is in an array, it will iterate the whole database.
We should look into just returning a $q.all with the lookup of the exactly keys instead of skipping, or if the keys lookup is cheap, find some heuristic to know when it's cheaper to use iterate vs. multiple getItem calls.
The text was updated successfully, but these errors were encountered:
Yeah, you'd have to set it up in a config block or something like that. I think there is a way to accomplish a similar thing as that extension, but I think we want to stick with vanilla localForage so we don't have to burden users with another dependency. Thanks for pointing that out, though! I'm sure there will be some useful things to learn from reading through that code.
Currently, even if you're only getting a single kv pair, if that lookup is in an array, it will iterate the whole database.
We should look into just returning a
$q.all
with the lookup of the exactly keys instead of skipping, or if thekeys
lookup is cheap, find some heuristic to know when it's cheaper to useiterate
vs. multiplegetItem
calls.The text was updated successfully, but these errors were encountered: