It does mean that the framework has to provide reasonable escape valves for the thing you're trying to do, and that won't always be true, especially if you're trying a more off-the-path experiment.
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.
-
Alright, I’ll write something up! Would an Ember slack be a good place to share it? I just don’t want to blast it out on public Twitter.
End of conversation
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.