For example, if you swap out QUnit for mocha in Ember, you won't be able to share as much testing infrastructure with the wider community, but most add-ons will work, development mode works, the router works, production builds work,
What featured of Ember Data did you find you needed when working with local storage. I bet we could do a better job giving guidance to adapter authors on best practices for making the code work idiomatically.
-
-
Tbf this was just for a hobby project just to see if I could get an Ember app running offline, so not a realistic case. For ember-local-storage it’s the fact that it focuses first on object and array storage, and models are further down and less emphasized. Some details of (cont)
-
(cont) getting it working were not clear, to me at least
-
Curious what was stopping you from using local storage directly in model hooks etc.
-
Reading the docs on https://github.com/rt2zz/redux-persist … Which examples were the most "copy-pastable" from the perspective of just quickly getting off the ground. There's a lot of warnings about config, but I'm guessing you found an example you could start with and ran with it?
-
The Basic Usage section covered my needs, which makes sense because all I’m doing is storing an array of trivial one-field objects. Need to run to a meeting but I would be happy to dig into this more, if you think this hobby project situation provides helpful ecosystem insight!
-
I think that hobby projects teach us a ton about what's important for conventions, so I'd love to dig in more.
-
For sure! Maybe I could do a brief writeup of the overall experience? Maybe I can share it privately b/c I don’t want to be publicly critical of add-on authors.
-
I'd love that.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.