Fork me on GitHub
#fulcro
<
2022-03-07
>
janezj08:03:50

I am going to create a web app to display server side events (iot). So websockets. Is this template good(preferred) starting point? https://github.com/Folcon/fulcro-template What is best practice to start a new fulcro project in general? to clone a template? clone old project. Or to cherry pick from old projects?

janezj13:03:10

... and it is 10 commits ahead and 15 behind.

sheluchin13:03:47

Yep. Unless you need something specific from there, I'd guess it's better to stick to the official.

janezj13:03:29

I will try to rebase, 3 files with conflicts

janezj16:03:23

I found a typo in https://github.com/fulcrologic/fulcro-websockets wrong: [com.fulcrologic.fulcro.networking.websockets-remote :as fws])) correct: [com.fulcrologic.fulcro.networking.websocket-remote :as fws]

sheluchin16:03:46

Pull requests are welcome.

💯 1
Jakub Holý (HolyJak)17:03:50

In general, the official templates are the recommended starting point.

👍 1
Richie23:03:00

Hey, what is this line trying to communicate from the fulcro book?

Note that our mutation's symbol is actually `app.mutations/delete-person`, but the first layer of evaluation (calling a mutation as a function just returns the call itself) will rewrite it to `(app.mutations/delete-person …​)`. 
https://book.fulcrologic.com/#_handling_mutations I don't understand the difference. I see a function call in the second case but I don't think that's the emphasis; or at least, I don't understand the emphasis.

Richie15:03:39

Oh, I think I understand. Where it says "rewrite it to" I read "it" as referring to app.mutations/delete-person but it's actually referring to api/delete-person. Thanks @U051V5LLP and @U0522TWDA , I think I was stumbling on the phrasing since I didn't understand enough the context well enough.

Jakub Holý (HolyJak)16:03:48

just call a mutation as a fn from the REPL and you will see what it does. Experiencing is best