Fork me on GitHub
Mark Addleman02:12:23

hi folks! i'm trying to work through the fulcro tutorial at and running into problems getting the remote server to work. It does not appear that the :started-callback function is being executed from the client. I have slightly altered the code to display an popup alert when the callback is executed but it never is:

(defonce app (atom (fc/new-fulcro-client
                     (fn [app]                                         ; (2)
                       (js/alert "hello!")
                       (df/load app :current-user root/Person)))))
where would i begin debugging this?


@UAMEU7QV7 Did you mount the app ? new-fulcro-client alone will not trigger anything. The execution happens in mount.

Mark Addleman00:12:51

Thanks. It turns out that was the problem.


If I have an edn prop in my components, that I want to make editable via a textarea, while keeping it checked via the form state clojure.spec helpers/etc. Is this the best solution?

:onChange #(do
                                        (fm/set-string! this :ui/query-params-str :value %)
                                        (when-let [v (util/safe-read-string %)]
                                          (fm/set-value! this :ui/query-params v)))
This way the map the is updated and is synced from the string value to the EDN one, when it is not partial like {:a "x


my problem with this is that parents of this component need to know about this -str suffixed attribute as well if they want to modify this child of theirs


Hi I'm noticing an error when I try deploying a basic fulcro app with advanced compilation. I followed the tutorial and it works in dev mode, but I get the following in advanced compilation:


I'm going to guess that I need to require my mutations.clj namespace somewhere in my clojure code path.


Yup! That was it.


Lein uberjar will throw out code any namespace that doesn't get required.


Ok now I have a different problem. I've deployed the jar to a vps and I'm getting 403 forbidden when the app tries to reach /api on the server. Any ideas why that is?


I wonder if it could be that I need to set my legal-origin config setting in config/prod.edn


Hmmm, I don't think that's it. I assume that is for doing api requests from somewhere other than localhost.


What could be different about my vps and my dev environment? I really don't want to get into using virtualbox and ansible right now.