Scott Trinh

Does this solve for the case where a user made a localForage instance on an old version? In my project, I'm not ever using `instance` or `createInstance`.

:tada: @hozkok for MVP! :tada: Thanks for the hard work!

@hozkok any update on the work you were doing to get this going? I'm happy to take it over since it seems like a really good feature that people want...

@MusicCog Alright, I'll stick it on my TODO list. Should be later this week that I have a patch. For those who are looking to use this feature, what problem...

@brunodeprez Thanks for the clarification. I'll take a look at this today and see if we can push this thing over the finish line.

Just wanted to drop a quick update here on my progress: As alluded to, the test coverage is a bit lacking, and I'm trying to be careful not to introduce...

Yeah, I imagine people would expect it to work like that. A kind of "three-way" binding where changes in the scope update the DB and also update any other scope...

@imwhocodes You could set up the notifications like this (from the README.md): ```js angular.module('yourModule', ['LocalForageModule']) .config(['$localForageProvider', function($localForageProvider){ $localForageProvider.setNotify(true, true); // itemSet, itemRemove }]); ``` And then in your controller, you...

~~Actually, that won't keep direct mutations in sync, just when using `setItem`. 🤔 Not sure that there is currently a way to do that, but I'll dive a little deeper.~~...

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...