so, the “easy” workaround @roklenarcic is to use component-local state for full-name during typing, and do your state updates (transact) on blur

@holyjak I added read-only form support (::form/read-only? on RAD master forms). So, now you can treat a form like a report. I’ll add the linkify stuff to it, as soon as I get some routing stuff added.

I should probably allow forms to just switch to read only mode based on the route param passed to them as well

I just pushed 3.1.23-SNAPSHOT of Fulcro. I’ve added some long-needed bits to the dynamic router, and updated the book. This is in preparation for building more complete routing into RAD as well. The new features are: • You can resolve the path to a target with (dr/resolve-path). This allows you to dynamically look up the route (a vector of strings) to a target at runtime. It does, however, require that you are careful not to use the same target in more than one place in your application’s tree. Doing so, of course, will cause it to only find one of them, and “which one” will not be obvious. RAD will use this in order to allow you to move RAD components deeper into the tree, and not just place them in the root router. • Reworked how will-leave works. If you don’t change your app, it should be 100% bw compatible, but the new stuff allows you to ask, anywhere in the app, if an on-screen target would block routing without potentially triggering a reaction from will-leave. This, of course, requires you rework your targets. The new support adds a :allow-route-change? option. See http://book.fulcrologic.com/#_targets_denying_routes_v3_1_23

This includes the new function can-change-route? as well, and also has a new component option :route-denied and helper retry-route!. The book explains how to use it all.

There are probably still little bugs, so I’m not releasing this formally just yet. I don’t expect the API to change, but I have to think about the dynamic query aspects of this, and I’m not sure I got them right.

Any idea why my router is getting nil props? This is the relevant part of the Root query:

...
:tem-organization/organization-number
 {:tem-organization/latest-bill-run
  [:bill-run/id
   {:ui/subscribers-list-router
    [:com.fulcrologic.fulcro.routing.dynamic-routing/id
     [:com.fulcrologic.fulcro.ui-state-machines/asm-id
      :minbedrift.ui/SubscribersListRouter]
     {:com.fulcrologic.fulcro.routing.dynamic-routing/current-route
      [*]}
     {:alt0
      [{:bill-run/subscribers
        [:br-subscriber/subscriber-id]}
       [:ui.fulcro.client.data-fetch.load-markers/by-id _]]}]}]}]}]

...
{:tem-organization/organization-number "979199325",
:tem-organization/latest-bill-run
{:bill-run/id 47143}}

Hm when I use StringBufferedInput component, the weird thing is that when the underlying model is nil my model->string function gets called with "" as the argument, which seem contrary to what you’d expect, I would expect the parameter to be nil.

how would I get emacs to properly align all of fulcros element macros arguments. by default if I have the argument map next to the element, it aligns the child element against the map rather than like it does in the examples like this

(div {:className "a" :id "id" :style {:color "red"}}
    (p "Hello")))

HTML5 routing just added to the RAD demo. Not super well-tested, but seems to work really well.

See @codonnell’s Blog post for some details that help understand the implementation if you read the source. https://chrisodonnell.dev/posts/giftlist/routing/ (this is on the develop branch of RAD demo)