RAD 1.2.6 adds :retain? to controls as an option. Look at that and see if it helps.

historically it has defaulted to true

https://github.com/fulcrologic/fulcro-rad/blob/develop/src/main/com/fulcrologic/rad/report_options.cljc#L188

or are you saying that “false” isn’t properly handled…that is also a possible bug 😄

This is the report logic that governs that: https://github.com/fulcrologic/fulcro-rad/blob/develop/src/main/com/fulcrologic/rad/report.cljc#L145

it’s a little complicated because controls can be local or shared (e.g. in containers)

and their value can come from the URL, app state, route parameters, default values, or the retained value.

I’m using enc/nnil to make sure non-nil values win, but perhaps there is a logic error you can spot/fix

It was a bug in 1.2.2. it works in 1.2.7

Thanks in advance for any advice, and apologies in advance if I am slow to reply as currently on a boat with very patchy networking). But it's been a good place to sit back and code 🙂

I use reitit with a slightly patched dynamic routing system, works great

I think it is a perfectly valid approach 🙂 I would love to see an implementation 😉

Thanks both. I will give it a try. I have a feeling it will make simple routing based on the user interface more difficult (e.g. panels / settings etc), but make it a bit easier to reason about parameterised paths and disconnect URLs from the user interface and so potentially keep a URL scheme that can remain backwards compatible even if the UI changes.

Just as a note: the DR system doesn’t tie to the URL itself. This was an intentional design decision because it can be used in apps that are not web-based. The URL scheme of mapping certain routes to URLs is therefore a user-defineable function. So the idea of bw compat is already designed in. In fact, it is trivial to make a helper (as RAD has) so you can route to a target component, so you could easily just keep a map from URL to target component, and route that way. Just sayin 🙂 See rad.routing:

(defn route-to!
  "Change the UI to display the route to the specified class, with the additional parameter map as route params. If
  route history is installed, then it will be notified of the change. This function is also integrated into the RAD
  authorization system.

  The `RouteTarget` should be a _leaf_ target. Fulcro will correctly route through all the parent routers - just
  make sure that `route-params` includes all the params that are needed.

  You may include `::rad-routing/replace-route? true` in route-params as a hint to the history that you'd prefer to
  replace the top history element instead of pushing a new one."
  [app-or-component RouteTarget route-params]
  (if-let [path (absolute-path app-or-component RouteTarget route-params)]
    (do
      (when-not (every? string? path)
        (log/warn "Insufficient route parameters passed. Resulting route is probably invalid."
          (comp/component-name RouteTarget) route-params))
      (when (not= :denied (dr/change-route! app-or-component path route-params))
        (if (::replace-route? route-params)
          (history/replace-route! app-or-component path route-params)
          (history/push-route! app-or-component path route-params))))
    (log/error "Cannot find path for" (comp/component-name RouteTarget))))

So,

{"/some/path" SomeComponent
 ...}

Thank you. That's really helpful.

Good question 😛 I don’t know.

seems like they should not make it back onto the wire

Weird

I notice that :not-found values get returned in Inspect, even though I'm using Pathom3, which doesn't use the :not-found key at all. Is it possible your observation is related, @U0522TWDA?