@pvillegas12 I think you copied serial? false from the demo when making the file upload remote

That is there to support parallel uploads of files, but it make that remote incompatible with ptransact!

making a remote automatically parallel means that any number of requests can go at once, and the defer relies on the serial blocking of the remote

I’m releasing 2.6.12 with a built-in error message to the console when this mistake is made

oh nice

I want to construct a presentational component (receives props and renders, nothing stateful) but I’m running into wanting to have UI only state in that component. I tried using a defsc and I can see the state changing in fulcro inspect but the component does not re-render based on that state change.

@pvillegas12 so i’m a little confused, could you provide a gist of the component?

if the component is not stateful, and you don’t need any react lifecycle methods, then you could just make it a function that takes arguments and returns dom elements, that’s very lightweight and simple

it’s not uncommon to have helper functions for that sort of thing

(defn labeled-input
  [{:keys [id className required placeholder help warning error success
           input-generator]
    :as   attrs} label]
  (let [input-group-classes (str (if required "required") (if error "error"))
        help                (first (keep identity [error warning success help]))
        help-id             (str id "-help")
        attrs               (cond-> (dissoc attrs
                                            :help :warning :error :required
                                            :success :input-generator)
                              help (assoc :aria-describedby help-id))]
    (div :$field {:className input-group-classes}
      (dom/label
        (dom/span label)
        (when help
          (dom/span {:id help-id} html/nbsp (str "(" help ")"))))
      (if input-generator
        (input-generator attrs)
        (dom/input (clj->js attrs))))))

@currentoor in plain react I would make a component that uses setState for changing a bit of state that is only concerned with the UI

in this case, it is a ui/currently-selected-model

ah i see so it does have state, but you don’t care about it

right

i would argue in most cases it’s still better to give it an ident and put it in app state

think about how you would program on the server

I gave it an ident too, but when I changed ui/currently-selected-model the fulcro inspect state changed, but the component did not get re-rendered

if you had some temporary state you need to track for a short period of time, wouldn’t you prefer having in the database? rather than some other mutable cell

my problem is the re-rendering

ah i see

well where is the mutation that triggers this update being called?

inside the component

hmm so when you call transact you’re using this from the component you want to re-render?

yes

however, when I call the factory function

I’m passing in props from the parent

(uses the same props)

so I don’t pass the normal (prim/get-query component-name)

that might be a problem

in fact i think the book says not to do that

if a component depends on data from app state (a component with an ident means it does) then it should have a query and only get the props for that query

My problem is that I have a big data blob I don’t want to be copying to diferent edges in the graph

unless structural sharing solves this

why? that’s pretty cheap operation with immutable data structures

i would at least try it

or only query for the things you need out of that blob in your modal

@wilkerlucio http://book.fulcrologic.com/#_interfacing_with_alternate_network_protocols doesn’t seem to be inline with pathom RC1. I”m getting complaints that the remote mutation I want to run doesn’t exist. Any ideas?