fulcro

Book: http://book.fulcrologic.com, Community Resources: https://fulcro-community.github.io/, RAD book at http://book.fulcrologic.com/RAD.html
tony.kay 2021-02-06T16:37:08.257300Z

I recently realized that I had not finished the history support update to Inspect. The current released version has a broken slider (could not view prior versions of db) and DOM preview in the DB tab. I’ve gone in an implemented the updates to those, and I’m happy to announce a new version of Inspect: 3.0.4. The Chrome store will auto-update after approval. For those wanting it sooner (or the Electron version), please visit: https://github.com/fulcrologic/fulcro-inspect/releases/tag/electron-3.0.4 https://github.com/fulcrologic/fulcro-inspect/releases/tag/chrome-3.0.4 NOTE: You MUST upgrade to Fulcro 3.4.16 (also just released) for the DOM preview fix.

❤️ 7
Alex 2021-02-06T23:33:01.260200Z

Hey guys, so I was going through the fulcro book regarding forms, https://book.fulcrologic.com/#_form_state_demos. I was playing w/ the first demo and on the inspector and noticed that ::forms-by-ident contained both of the form-state for phone 1 and 2. My question is, is it good practice to remove form-state from ::forms-by-ident given that you've finished editing the phone?

Alex 2021-02-07T22:24:23.272800Z

Gotcha, thanks for the reply.

Alex 2021-02-06T23:33:55.260300Z

I'm just picturing a scenario where you have a table w/ editable rows and thinking it'd keep a lot of form-state inside ::forms-by-ident even though I might not need it.