For those of you wanting to try the new Inspect in chrome: https://github.com/fulcrologic/fulcro-inspect/releases/tag/chrome-3.0.0-RC1

remember this requires Fulcro 3.4.0-SNAPSHOT or better

I fixed the db flicker in this version

I’ll be releasing a electron update shortly

https://github.com/fulcrologic/fulcro-inspect/releases/tag/electron-3.0.0-RC2

Fulcro 3.4.0 is now on Clojars. This version requires the new version of Inspect (released above). • Upgrades inspect protocol for less dev-time overhead, which also fixes bug where db goes blank in inspect • Fixes a regression with computed props on targeted updates • Fixes UISM load’s spec to allow for nil as the query component (which matches df/load)

I am going to hold off on the Chrome store release of Inspect for a while (I don’t want people that don’t follow the channel to be surprised by inspect “breaking” on their older Fulcro app), but it is easy enough to manually upgrade the Chrome extension using the release of Inspect above.

I’ll be placing a “legacy” version of the chrome plugin in releases, so when I do upgrade it people will be able to easily downgrade.

For reference, here is that legacy version for Chrome: https://github.com/fulcrologic/fulcro-inspect/releases/tag/1.0.21

trying out the new error-boundary macro in a cljc, and the JVM repl complains: No such var: com.fulcrologic.fulcro.react.error-boundaries/￱*￱error-header￱*￱ I guess we need to define these vars ourselves for cljc?

@kevin842 could be I just forgot something for cljc

ah, there is at least one problem with the error boundaries…dom should not be a hard dep there, or it won’t work with native 😕

I’ll do bit more testing against CLJC files with both DOM and native. I think I was developing that one with only DOM in mind, and didn’t refine it quite enough

Fulcro 3.4.1 on clojars. Cleans up error boundaries so they can be used in mobile. Fixes a custom type issue with the new inspect.

Also released an update to the F3 port of workspaces https://github.com/awkay/workspaces with a fix for test card types supplied by @frederic (version 1.0.2)

There might have been a typo in the book (in the "4.6.2. Fulcro 3.2 Inputs" section): http://book.fulcrologic.com/#Inputs32 > The mutation helpers in the mutations namespace (toggle!, set-string!, set-integer!, and set-value!) use transact!!, so they will all function properly.

In the source code, set-value! etc. use transact! not transact!!

Plus the quoted sentence above contradicts with a sentence couple lines down: > The mutations namespace now also includes set-string!!, set-integer!!, etc. These are identical to their single ! counterparts, except they use synchronous transact!!.

correct