That API is not finalized, and should be richer. Of course you should be able to use an existing state machine. You should also be able to supply the actors on initialization. The current API is just a draft to scope out the general shape

yes, I understood it's very much in flux still. it was just an fyi. I'm experimenting myself now with a small macro to step through a "spec" with events on the various state machines in my app. It's really nice!

fun

could you please explain a little more what you mean? set to nil in the client db when not found in Pathom?

yup, doing what you would use merge/nilify-not-found for, but less manually

But sweep-merge does that already, no?

or do you want, instead of removing the data from the client db set them to nil? If so, why? The common clojure best practice is to omit the keys instead of using nil values.

not sure what you mean by removing. what I mean is, when you have :query [{:foo [:bar]}], when you load that component, if pathom returns nil for :bar, :bar will have the value of ::merge/not-found in app state, unless you nilify it in explicitly pre-merge

https://clojurians-log.clojureverse.org/fulcro/2020-05-09/1589057191.115500

https://clojurians-log.clojureverse.org/fulcro/2020-05-17

some prior discussion

> will have the value of ::merge/not-found in app state by app state, do you mean Fulcro client DB? sweep-merge called by merge-tree and merge-mutation-joins , which are both called by merge* , does remove such data from the client DB. From your question I guess your problem is that Fulcro marks as not-found and thus removes some data you do not want removed and you are trying to prevent that by getting rid of those not-found? From the previous discussion: > marking fields as ::merge/not-found even though they are being queried for that is the whole point, if you query for a prop and Pathom has no data for it then Fulcro will mark it as not-found via mark-missing Ah, I see > the server is responding with those keys in the map, but their value is nil.

What is the bigger problem you are trying to solve? What do you want? You want the server to return nil and Fulcro then to store nil into the client DB? Why would that be different from simply removing the corresponding prop from the client DB? Since (= (get {:k nil} :k) (get {} :k)) ?

still not sure what you mean by remove. I'm loading data, e.g. bar, and I might like to use bar in render like (map fn bar), and that blows up if bar is a keyword but works if it's nil

at no point am I thinking about deleting data from the client db; I just want to use the data I loaded without any surprises

that being said, there actually is a use case I have for nil value vs no key: caching

e.g. don't load keys that have already been loaded. if nil is never merged, then I don't know that that key has already been loaded

Remember how Fulcro works. Loads puts data into the client DB (and it can also remove data, ie entities and their props from there). Then Fulcro gives your component props based on the client DB. Are you saying that you see :not-found in the props of the component?

ah, I see now. and yes, ::merge/not-found tries to get rendered

That is weird. And you say that doing what you did in pre merge prevents it? But pre merge only influences what data comes into the client DB and props come from there. So what is the diff in client DB in the two cases (with and without pre merge nillify)?

yes, nilify-not-found in pre-merge (what @dvingo posted in the later log I linked above) will result in the nil returns having values of nil in the client db/props, instead of ::not-found.

not sure what you mean by "only" influences the client db data. is there a larger scope you're thinking of?

It's been a while, but I think I was passing the data in pre-merge to an entity construction function that had guardrails annotations and the ::not-found values were causing the instrument check to throw. I used this helper to remove them: https://github.com/dvingo/my-clj-utils/blob/master/src/main/dv/fulcro_util_common.cljc#L169 I suppose you could try incorporating this helper in the :global-eql-transform of the fulcro app to get this as default behavior.

I mean that load and pre-merge have in a way nothing to do with the props your component sees. They only affect what data ends up in the client DB. Then, when you render, Fulcro reads from the client DB to construct the props for the component. So if you are saying there is a difference then there must be a difference in the data and the client DB. What is it?

holyjak, the difference is between pathom's return value (nil) and the value I recieve in pre-merge/client db/props (which are all the same, ::merge/not-found)

didn't know about :global-eql-transform, thanks