I would think this is app-specific (when is data to be considered stale?) and there is not built-in way to do it. But you could construct your own variant of df/load with the requisite behavior. Not sure that would make your code simpler. If you go this way, I would be happy to see the code 🙂

Gotcha, thanks for letting me know there isn't yet a way to to do this. If I like what I come up with, I will post it here.

There is a namespace (alpha) in Fulcro for doing this…well, in a way: See com.fulcrologic.fulcro.offline.load-cache but perhaps that isn’t quite what you meant (that would let you cache data over multiple sessions).

The basic idea of the offline support is just that: be able to load stuff when there is no network, but only if it’s been seen before (e.g. get me the most recent version of X). The durable mutation support goes the other way: save idempotent mutations for later sending to the server when back online.

So Jake could use com.fulcrologic.fulcro.offline.load-cache/load-eagerly! which would return at once if the value is already cached - but contrary to what he currently does, it would still call the server to refresh the cache. Right?

right. It’s configurable and you could also just treat it as an example of how you can muck with the internals to do whatever you like.

(defmutation load-if [{:keys [load? load-args] :as params}] (action [{:keys [state app] :as env}] (if (load? state params) (apply df/load! (into [app] load-args)) (let [{:keys [post-mutation post-mutation-params post-action]} (last load-args)] (when post-mutation (comp/transact! app [(post-mutation (or post-mutation-params {}))]))` (when (fn? post-action) (post-action env)))))) (defn load-if! ([app server-property-or-ident class-or-factory] (load-if! app server-property-or-ident class-or-factory {})) ([app server-property-or-ident class-or-factory config] (let [{:keys [load? routing-ident]} config load-config (cond-> (dissoc config :load? :routing-ident) routing-ident (assoc :post-mutation dr/target-ready` :post-mutation-params {:target routing-ident}))] (comp/transact! app [(load-if {:load? (or load? (constantly true) :load-args [server-property-or-ident class-or-factory load-config]})]))))

Thank you for the suggestions. I'm not sure I need to go the offline route at this point, but I may need it in the future.

sure

does https://github.com/fulcrologic/fulcro-i18n fit the bill?

I think that's localization and not localized dom. A bit of term overloading. localized dom is, If I understand correctly, for localizing things like css with components.

specifically I'm referring to the ns fulcro.client.localized-dom

presently rad uses com.fulcrologic.fulcro.dom(-server) namespaces (as well as corresponding semantic ui ns s)

nevermind

just realized I inadvertently was on an old fulcro docs

Now I'm looking at the proper docs and they are pointing me to fulcro-garden-css and I'm getting the same instructions. So I am back to lost again on how to have localized css in the rad project. The whole 'usage' section has me a bit confused. So I'm not sure if I'm just doing it wrong or if RAD requires a different approach for colocated css

Does (locdom/div {:classes [header-logo]} "test") - ie both with props and a child - work? IMO localized-dom should work with RAD in the same way as it does with non-rad. Perhaps try to get it working in a plain fulcro app first?

According to https://github.com/fulcrologic/fulcro-garden-css/blob/develop/src/main/com/fulcrologic/fulcro_css/localized_dom.clj#L12 it seems to me that passing 2 args to emit-tag should be just fine...

Realized my errors. Thanks for trying to help!