fulcro 2022-03-08 | Slack Archive

dvingo03:03:06

the mutation is a type which implements IFn: https://funcool.github.io/clojurescript-unraveled/#participate-in-clojurescript-abstractions https://github.com/fulcrologic/fulcro/blob/9d9ac36672e6a7fb9bdf8fb835f8a30b145ce116/src/main/com/fulcrologic/fulcro/mutations.cljc#L74

👆 1

Jakub Holý (HolyJak)09:03:50

> I see a function call in the second case There should actually be '(app.mutations/delete-person …) - ie it is not fn call, it is a list with a symbol and a map. See https://fulcro-community.github.io/guides/tutorial-minimalist-fulcro/index.html#_changing_global_data_and_performing_remote_calls_mutations You could also do the self-paced https://github.com/holyjak/fulcro-intro-wshop, I think we run into this there. I can be revealing to just call the mutation as a function from the REPL and see what happens.

danieroux09:03:24

(df/load
    app
    [{[:asset/id 13] [:asset.series/level]}]
    asset-graph-component
    {:params
     {:time.series/from #inst "2021-12-11"
      :time.series/to #inst "2021-12-16"}})

New to Fulcro, trying to make sense of things: If I want to graph the time series data of something, is this the shape of how it could be?

✅ 1

danieroux11:03:48

[({[:asset/id 13] [:asset.series/level]}
  {:time.series/from #inst "2021-12-11T00:00:00.000-00:00",
   :time.series/to #inst "2021-12-16T00:00:00.000-00:00"})]

And this is the EQL that Pathom3 should be able to work with @U0522TWDA ? The df/load that generated the above, was this in the end:

(df/load
    app
    [:asset/id 13]
    asset-component
    {:params
     {:time.series/from #inst "2021-12-11"
      :time.series/to #inst "2021-12-16"}})

With [:asset.series/level] being the query on the component.

Jakub Holý (HolyJak)11:03:11

LGTM

Jakub Holý (HolyJak)11:03:10

Ah, sorry, yes, df/load does a join on the keywrod/ident and query of the component you give it. I should have pointed that out.

Jakub Holý (HolyJak)11:03:44

I am a little surprised to see asset-component , I would expect AssetComponent as CamelCase is the normal naming syntax for defsc. Makes it easier to see when we are talking about "classes" and when about instances or elements.

danieroux11:03:41

Yeah. There are many moving parts in this conversation 😕 I am spiking if we can move a hooks-based app over to Fulcro, bit by bit. So I'm in com.fulcrologic.fulcro.raw.components world.

👍 1

danieroux11:03:35

Right now I am wrapping my head around getting pathom3 to extract those parameters out of that EQL. Thank you for sense-checking that it looks good!

Jakub Holý (HolyJak)11:03:49

Are you planning on keeping hooks or using classes? Both work fine with defsc.

Jakub Holý (HolyJak)11:03:09

> wrapping my head around getting pathom3 to extract those parameters out of that EQL. we had a discussion about that recently here

danieroux11:03:16

Planning on keeping hooks

👍 1

Jakub Holý (HolyJak)11:03:44

see https://clojurians.slack.com/archives/C68M60S4F/p1646084327420159?thread_ts=1646081061.832729&cid=C68M60S4F Not sure whether this is P2 or P3 but expect them to be similar