Clojurians Log v2

Got it. Many thanks for sharing your thoughts.

@reshef.mann Are you using Fulcro version 3.4.2+? The latest Fulcro Inspect requires that to work.

@henrik I'm using fulcro version 3.4.3 and fulcro inspect version 3.0.2 and see the same issue.

@dionysius.almeida The issue is strange because Fulcro Inspect is working fine for me... Make sure your Chrome version is up to date as well. Try setting "Site access" to "On Click" in your Fulcro Inspect extension settings. This way, when you use Fulcro Inspect, you need to click on the Fulcro Inspect extension icon to "activate" it. From your screenshot, you should click on the puzzle icon towards the right end of your navigation bar, then click on "Fulcro Inspect". Hope that manually turning on Fulcro Inspect can solve your issue of it not working all the time. The bright side is that you could still get it to work somehow, despite the workaround (i.e. closing and opening it again). Hope you can find a solution. P.S. You @ a different person, not me. I am @hk9861.

@hk9861 Thank you for your help. Yes I did @ a different person 😀. I did change it to "`On Click`" but it's the same result. I guess I will have to live with the closing and opening developer tools for now.

@hk9861 Thanks! I was indeed using and older version (I cloned the fulcro template). It works fine now.

I have a problem coming up with a good solution to compose mutations. Like doing a redirect after a successful sign up. In 9.3.9. Result Action for Pessimism there is an example where you submit a new mutation in the ok-action section, thats what I always did. But what if I don’t always want to redirect? Having a sign-up mutation and a special sign-up-and-redirect mutations seems odd. I have the feeling I am missing something here…

So what I can do is doing the redirect based on the application state. This is fine when I can redirect if, for example, I have a valid session in the state after a successful login. But this seems quite cumbersome in some situations. (like if the remote mutation changes some text and I would have to compare the old and new state for changes)

You can compose st->st functions: https://book.fulcrologic.com/#_mutation_helpers

If they are what you want consider also using:

[com.fulcrologic.fulcro.algorithms.normalized-state :refer [swap!->]]

Thanks, but this does not help with mutating based on the result of another mutation. I don’t want to write something like this:

(defmutation sign-up [{:keys [username password]}]
  (action [_] (do-whatever))
  (remote [_] true))

(defmutation sign-up-with-redirect [{:keys [username password]}]
  (action [_] (do-whatever))
  (remote [env] (m/with-server-side-mutation env `sign-up))
  (ok-action [_] (comp/transact! [(redirect!)])))

(defmutation sign-up-with-confirmation-alert [{:keys [username password]}]
  (action [_] (do-whatever))
  (remote [env] (m/with-server-side-mutation env `sign-up))
  (ok-action [_] (comp/transact! [(show-confirmation!)])))

I didn’t know about swap!-> . Thanks

I want to set up a very basic GitLab CI pipeline just to execute my tests. Any pointers as to how to implement that?