This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # arachne (1)
- # beginners (22)
- # boot (21)
- # cider (23)
- # cljs-dev (16)
- # cljsrn (9)
- # clojure (118)
- # clojure-dev (11)
- # clojure-greece (16)
- # clojure-italy (10)
- # clojure-losangeles (4)
- # clojure-russia (14)
- # clojure-serbia (4)
- # clojure-spec (58)
- # clojure-uk (33)
- # clojurescript (30)
- # cursive (17)
- # datomic (48)
- # docs (22)
- # events (1)
- # fulcro (24)
- # hoplon (3)
- # jobs (6)
- # jobs-discuss (4)
- # keechma (4)
- # leiningen (11)
- # luminus (4)
- # midje (1)
- # off-topic (107)
- # onyx (30)
- # other-languages (12)
- # pedestal (4)
- # re-frame (72)
- # reagent (6)
- # remote-jobs (1)
- # shadow-cljs (16)
- # spacemacs (3)
- # specter (9)
- # uncomplicate (4)
- # unrepl (40)
So you could have that code be your mutation, and it calls other 'mutations', which are not mutations but state->state transformations.
Part of what I need to do is affect something on the server side. The state->state transformation would work otherwise.
@grzm so, if you are trying to chain calls to
transact! the general advice is to adjust your thinking and see if you can write it as a single thing instead. The chaining leads to complexity in code that may not be necessary. The supported chaining is on true mutations (not loads) via
ptransact!. The book covers this.
If you see no other way of avoiding submitting a new transaction on a post-mutation from a load, then submit a new one with
transact!. The general recommendation, though, is to use something like https://google.github.io/closure-library/api/goog.async.nextTick.html to defer it until the current transaction processing is complete. Pretty sure we recently made the reconciler available in the
env in the post mutations (it is usually available in the env of regular ones as well)
wow i love the effort put into helping ppl learn about fulcro, via videos, tutorials, etc…
I also expanded the html-entities namespace to include all of the well-know entities that are used in HTML for easier use in React
@tony.kay Yeah, that's what my gut was telling me, and it's definitely in pursuit of working around another issue, rather than a desired design. I'm having trouble moving (i.e., creating, disposing, and creating anew) a KeyboardShortcutHandler between items of a list (currently working up a test case).
@grzm I would expect shortcut handlers to be something you mess with on mount, no? Standard React lifecycle stuff.
(fulcro.events/page-down? some-key-code-event) (dom/span nil (str "A dagger: " fulcro.ui.html-entities/Dagger))
@tony.kay Yeah, I'm creating them in
componentDidMount and calling
componentDidUpdate. I can see that they're no longer active (via
.getDisposed), but the wrong triggers are getting called on the key events.
I just created my own network implementation and I needed the app inside my network object. In all the examples there is a
complete-app property in the network record which never get's filled. Is this just old cruft or is there something wrong?
in the past Fulcro had a
start on the network that used to receive the app, but at some point that ended up being a circular reference and had to be dropped
there is no good way AFAIK to handle, what I have done is to inject it later, you can send an atom to the network, and on your
started-callback you can set the atom content to be the app, so after that the network can deref and read it
I did exactly the same ^^
how hard is it to use sablono with fulcro? I don't mind paying a small perf. penalty to avoid all this
@chrisblom should work fine. I think some people have problems with it and SSR, but I don’t use it so I can’t say.