yes this websocket component looks better 🙂 more questions: - (1) is there an easy migration path from om next to fulcro? - (2) it looks like fulcra can do SSR like om next - is there an example somewhere? In om next I instantiate a reconciler etc. and embed the initial state in the html page (looks fulcra does something similar) - (3) are there ways to manipulate the page from inside the component? Adding css/js dependencies for instance? (there are separate solutions in the react ecosystem like react-helmet, in clj https://github.com/bluekezza/jet which was made by a former coworker)

@tony.kay I’m running into trouble with trigger-remote-mutation. It seems use :remote for ::uism/mutation-remote even if a different value is set.

Also, are there any known issues between pathom and fulcro.incubator.ui-state-machines?

@levitanong hm. I’d have to look at the mutation remote…it is a synthetic mutation that should be using that for the remote. UI state machiens and pathom have nothing really to do with each other, though of course bad return values from a parser (e.g. your return values) can cause all manner of issues.

Make sure uism is aliased…that would break your remote thing

yeah, it’s aliased

:remote is the default, so if your keyword is wrong for the option, then it will revert

Turn on debug logging…there is a debug statement that says if it sees an explicit mutation remote

I’m looking at fulcro-inspect, and this is one one of the parameters for fulcro.incubator.pessimistic-mutations/start-pmutation: :fulcro.incubator.ui-state-machines/mutation-remote :arcgis

I’ve had to duplicate my :arcgis remote to also be the value of :remote to proceed

Will try the debug logging

One odd thing i noticed: when i run the query in fulcro-inspect:

{app.api.mutations/hydrate-place-location
 {:com.wsscode.pathom.core/reader-error
  "Mutation not found - {:mutation app.api.mutations/hydrate-place-location}"}}

no idea what that is…that all sounds like your code

and you’re not looking for start-pmutation…that is the local side of pmutate…you want mutation-delegate

thing is, it worked without pessimistic-mutations

this particular bit jumps out: {:mutation app.api.mutations/hydrate-place-location} could it be that pessimistic mutates wrap the symbol with an object?

my mutation-delegate has identical parameters as start-pmutation

srorry, I don’t have time to debug this with you. Here is how it works: You do you the trigger, and it builds a “fake” pmutation. It calls pmutate on this handler, basically: https://github.com/fulcrologic/fulcro-incubator/blob/develop/src/main/fulcro/incubator/ui_state_machines.cljc#L725 The handler is on the real low-level Fulcro multimethod that defmutation emits defmethods for. As you can see on line 730 and 744 it uses the parameterized remote for the remote if it is there, and :remote if not.

lines 738 and such do the rewrite of the AST so it “looks” like the mutation you want to the server

and all of the SM-specific params are stripped out of the AST params there too

line 783 is where it take the symbol of mutation decl and turns it into a parameter

so, if you find an error in any of that, let me know…but that’s how it works

alright, thanks for your time @tony.kay! I’ll digest this.

it always uses the same mutation internally, and that mutation rewrites the server AST for network interaction

@tony.kay Even if the explicit remote is set, all the :fulcro.client.impl.data-fetch/deferred-transaction have remote = :remote, which is what causes the error complaining about an invalid remote :remote:

VM25797:57 explcit remote is  :arcgis
VM25797:57 explcit remote is  :arcgis
VM25797:57 explcit remote is  :arcgis
VM25797:57 explcit remote is  :arcgis
VM25797:57 explcit remote is  :arcgis
VM25797:57 explcit remote is  :arcgis
goog.debug.console.js:203  [104.949s] [fulcro.client.impl.application] Use of invalid remote(s) detected!  #{:remote}

[:fulcro.client.impl.data-fetch/initialize nil]
[:fulcro.client.network/abort-id nil]
[:fulcro.history/tx-time 282]
[:fulcro.client.impl.data-fetch/uuid "87489027-66b8-43b0-8d57-666ec92a7c83"]
[:fulcro.client.impl.data-fetch/parallel false]
[:fulcro.client.impl.data-fetch/target nil]
[:fulcro.client.impl.data-fetch/original-env {}
]
[:fulcro.client.primitives/ident nil]
[:fulcro.client.primitives/remote :remote] ;; what i'm guessing is causing the issue
[:fulcro.client.primitives/query [:fulcro.client.impl.data-fetch/deferred-transaction]]
[:fulcro.client.impl.data-fetch/refresh [:fulcro.client.impl.data-fetch/deferred-transaction]]
[:fulcro.client.impl.data-fetch/type :ready]
[:fulcro.client.impl.data-fetch/post-mutation-params {:tx [
(…)
], :ref [:sidebar :root], :reconciler {}
}]
[:fulcro.client.impl.data-fetch/fallback nil]
[:fulcro.client.impl.data-fetch/marker false]
[:fulcro.client.impl.data-fetch/post-mutation fulcro.client.data-fetch/run-deferred-transaction]
[:fulcro.client.impl.data-fetch/field nil]

feel free to open an issue on incubator with a small repro case

I must be doing something wrong. When trying to compile the first thing from the docs in a REPL:`

(ns common.admin.ui.root
  (:require
   [fulcro.client.dom :as dom :refer [div]]
   [fulcro.client.primitives :as prim :refer [defsc]]))

(defsc Root [this {:keys [root/message]}]
  {:query         [:root/message]
   :initial-state {:root/message "Hello!"}}
  (div :.ui.segments "hello"))

1. Caused by java.lang.RuntimeException
   No such var: fulcro.client.dom/macro-create-element*

@nha Om actually has a bug in DOM that makes it inefficient…you can’t make the dom things both functions and macros in the same ns across both langs…it’s a known issue, and Fulcro fixes it, but there is no way around needing conditional requires to make it work right

So, even though it says you’re getting macros for div in the source, if you actually look at the output your getting function calls

You can’t define clj macros AND cljs macros in the same cljc file (if you also need function versions of the same thing)…just can’t be done (with all of the constraints that DOM has…you also NEED function versions, in case you use them as values).

well you can check if the macro is supposed to emit CLJS or CLJ code though

so to be more clear: you can’t have function AND macro versions of BOTH clj and cljs thing in one file

f that acts as both a function and macro in one file for both langs

You’re the magician @thheller…but I don’t think that’s a rabbit even you will pull out of a hat 🙂

(I beat my head against a wall for days before asking D. Nolen..since I thought he had written it into Om Next…that’s how I determined what was being done was not written by him, and did not work; well, I had determined that it didn’t work when I tried to write it, I just couldn’t figure out how his did…turned out it didn’t)

maybe I missed something

#?(:clj
   (defmacro foo [& bar]
     (if (:ns &env)
       :cljs
       :clj)))

but this works

that’s fine, yes

now make a function foo that can be used with (apply foo ...)

for both langs

in the same file

yeah that is not possible

exactly 🙂

but it is necessary because you need to be able to use dom things as functions sometimes

but ideally most of the time you get macro expansion for speed

in Om Next, you get functions most of the time because the implementation is wrong

well, I don’t remember under what circumstances…but whatever 🙂

in any case thanks for the explanation 😄

sure

just didn’t want you thinking “well it works in Om Next” 🙂

lol. To be clear, my understanding of Om next is still pretty limited

oh, I thought you were porting an existing Om Next app

I am 😛 not saying it’s a big app or anything. I wrote it, but it is pretty basic

I basically liked the colocated queries and that’s about all I used. That and colocated CSS (I remember making a PR to a precursor to the CSS in fulcro)

ah - looks like dom/render-to-str is gone

oh. dom-server again 🙂

Did you watch any of the videos?

also this: http://fulcro.fulcrologic.com/vsom-next.html