The state machine on reports is completely pluggable. Just copy the provided one and modify the bits around loading.

Where do you get this idea? There is code to support doing so, but it is not required. You can do whatever you like.

I recall reading that in the docs but it might be a false memory

I fetch data after entering a route. It does work, but I feel like it's definitely not the path of least resistance.

Perhaps I should post on #C87NB2CFN instead, because it feels as if this is more of an issue with parameters in pathom on idents - which from https://edn-query-language.org/eql/1.0.0/specification.html#_parameters the documentation, should be supported on idents? It's then an issue of how to get those parameters into an attribute resolver - perhaps they should end up accessible via (pco/ident-params env) as an equivalent to (pco/params)?

PS. I did manage to get the parameters through using :update-query - just needed to add the params to an attribute that wasn't the same as the original ident attribute.

Why aren’t you using load’s :params option?

Each element of a query can have params, and generally you only need params on the top for a load, which it will do. Then you can add a plugin to pahtom to pull those out into the env

https://cljdoc.org/d/com.fulcrologic/fulcro-rad/1.0.3/api/com.fulcrologic.rad.pathom#query-params-to-env-plugin

and there is no “3rd element of an ident is params” support in EQL…not sure where you’re getting that

A proper EQL query on an ident, with params, looks like [{([:thing/id 1] {:x 1}) [:subquery]}]

but again you’re better off using the :params option on load and the plugin for pathom

Thanks @U0CKQ19AQ - yes I copied it across incorrectly. I had also tried using :params but they weren't brought in because I hadn't worked out how to add the plugin into pathom - but I'll copy it from fulcro rad - thank you!

For any future readers, for pathom3, one registers a plugin for wrap-process-ast in order to process the AST and take any parameters and make them available to all your resolvers via the environment:

(-> env
      (assoc ::p.error/lenient-mode? true
             :com.wsscode.pathom3.format.eql/map-select-include #{:tempids}) ;; always include request for tempids
      (pci/register ops)
      (p.plugin/register
       {::p.plugin/id `query-params->env
        ::p.eql/wrap-process-ast
        (fn [process]
          (fn [env ast]
            (let [children     (:children ast)
                  query-params (reduce
                                (fn [qps {:keys [type params] :as x}]
                                  (cond-> qps
                                    (and (not= :call type) (seq params)) (merge params)))
                                {}
                                children)
                  env          (assoc env :query-params query-params)]
              (process env ast))))}))

How can EQL possibly know “which player’s name” without an ident?

Likes like me asking “favorite color?” in a crowded room with my eyes closed…who should answer?

If you use load-field! within a component, then it will automatically write the ident join for you, if that’s what you mean, but of course it uses “this”’s ident, which would need to be a specific person in your case

Load also supports things like focus query and query transforms, but load itself is primarily concerned with loading entire entities. load-field! is the special case of pulling a single thing (which may have a subquery)

Yes load-field! is exactly what I was looking for. Thanks!

In order for rendering to know what to refresh, you do have to query the statechart itself (e.g. the ident of the statechart in question), then yes, you can use the statechart configuration, and every time it changes the component will render.

The chart configuration is definitely a thing to use in the UI. One other note: You can do a link query on jst the “table” name of statecharts in general. That’s fast to query on, though the componentShouldUpdate check will be a little slower then.

And if I use the configuration then what's the best way to display the right ui component? A giant cond expression?