3.0.0-alpha-5 is on clojars. I fixed a problem with inspect, added support for mutation joins via returning et al. Basically these releases are slowly adding little bits that got missed here and there. This release also adds back support for explicit initial state (not component-based) which is used by some apps…particularly demos, though I change the API just a bit…see docstrings if you use that.

I’ve ported a number of the book demos. So far it has mostly been just changing namespaces and minor updates here and there.

The following are now known to work (because I tried them): - Union Router - The older dynamic router, including loading on code splits. API will change here a little, since we have a component registry now…no extra multimethod needed. - I’ve partially tested the new dynamic router (and by proxy UI state machines), but not heavily…and the docs need updated because fewer macros are needed. - Supplying an alternate initial state to an app as a normalized db - Mutations that return things w/targeting - Data fetch in general There is preliminary support for ok-action and error-action in all mutations, though it is not documented. The env contains a lot more stuff than it used to, so you can find things like the raw network result, status code, original query/tx, etc.

I’ve got a new lein template app written, but not integrated by into the template itself. The temporary repo where I’m building the content is here if anyone wanted to clone it as a starter: https://github.com/fulcrologic/fulcro3-template

I have an interesting issue where on submit of a form (fs/dirty-fields etc..). I’m not seeing the updated subform values until I also update a parent form value, then I will see both values in the diff. Any ideas?

Hello, I was wondering if there's a recommended way to add specs to a component's props?

@jtouron Well, if you’re using namespaced keywords, then it is a simple as doing an s/def on that keyword

if you mean “how do I check the specs”, well, that is a runtime overhead that you would not normally want, but you could easilly just do an (assert (s/valid? (s/keys :req […]) props))

If you mean “how do I *automatically make it so all of my components check their props” the answer is “write a macro…it’s lisp”

Fulcro 3 (in alpha) has render middleware where you could probably automate this as well…have to think abt it (which I’m not going to do right now 😉 )

@tony.kay Thanks for the response. I was thinking about just doing a (s/assert ::props props) after the component's options map, which sounds similar to what you suggested, but was just curious if maybe someone had a better way. One last question: Is there a way to set the value of clojure.spec.alpha/*compile-asserts* when shadow-cljs compiles? The documentation says that the value of 'clojure.spec.compile-asserts' system property can be set, but I believe that's JVM only and I don't know if that translates somehow to shadow-cljs.

@jtouron I would suggest you look at gnl/ghostwheel

I use it for my projects to deal with the issues of instrumentation, and really like it

in answer to your specific question: don’t know off top of my head

@tony.kay Will do, thanks again for the help.

Alpha 6 is on Clojars:

3.0.0-alpha-6
-------------
- Added official hooks to a number of places, and added a bit to docs
- Finished defining the "default" amount of pluggability for default mutations
- Make global query transform apply closer to the network layer to catch both mutations and queries
- Added confirmation tests to some more elements of merge join and pre-merge
- 

The big add here is that now when you create an application there are a number of “hook points” where you can customize functionality. See the docstring on fulcro-app in applications.cljc.