3 ms·
Nailed it. Not only do I share the same sentiments, I have also had a very similar experience with 3. Specifically, I like to be able to interact/test with my
by kingdomcome50 7y ago
Nailed it. Not only do I share the same sentiments, I have also had a very similar experience with 3.
Specifically, I like to be able to interact/test with my application as I build it in the console. I have had much success with wrapping my "Action Creators" in a API of sorts and mounting it to the `window`. This saves me from having to either create some sort of one-off component to "get at" some piece of functionality or hand-rolling actions in redux dev tools.
- karatestomp 7y agoI've done similar things, and yeah, it's great for making quick-n-dirty utilities to poke around with your data & state handling code. You can even throw ugly non-React GUIs on top, trivially, including in something like Electron (if, say, your application needs access to functionality or modules not available on the Web, as could be the case for certain Javascript deployment targets like mobile, set-top boxes, desktop, server, and so on).