I'm new to fulcro (and React). I am creating a todo list app as a learning exercise. I want to write a fulcro component that accepts text from the user and adds that text as a new item in the todo list. I'm having trouble setting the properties on this component:

(defsc NewTodoItem [this {:todo/keys [id label]}]
  {:query [:todo/id :todo/label]
   :ident :todo/id}
  (dom/form {:onSubmit (fn [x]
                         (.preventDefault x)
                         (prim/transact! this [(new-item! {:todo/label label})]))}
            (dom/fieldset :.field-group
                          (dom/input {:type     "text" :value label
                                      :onChange #(m/set-string! this :todo/label :event %)
                                      :onBlur   #(prim/transact! this [(new-item! {:todo/label label})])}))))

Correction: I fixed the ident. Now I don't get the error message but the set-string! doesn't seem to do anything.

(defsc NewTodoItem [this {:todo/keys [id label]}]
  {:query [:todo/id :todo/label]
   :ident [:todo/by-id :todo/id]}
  (dom/form {:onSubmit (fn [x]
                         (.preventDefault x)
                         (prim/transact! this [(new-item! {:todo/label label})]))}
            (dom/fieldset :.field-group
                          (dom/input {:type     "text" :value label
                                      :onChange #(m/set-string! this :todo/label :event %)
                                      :onBlur   #(prim/transact! this [(new-item! {:todo/label label})])}))))

@mark340 Hi! Could you elaborate a little bit on the “doesn’t seem to do anything”? Did you inspect the database (using the inspect Chrome extension) and saw no value there?

ah actually nevermind; your issue is due to how you are invoking the new todo item component

(new-todo-item {:todo/id :new :todo/label ""}) if you do this the prop :todo/label will always be ""

it will never update with the set-string! mutation

Ah

what's the right way to call it?

try something like this:

defsc NewTodoItem [this {:todo/keys [id label]}]
  {:query [:todo/id :todo/label]
   :ident [:todo/by-id :todo/id]
   :initial-state {:todo/id :new :todo/label ""}}
...)

(defsc Root [this {:keys [new-todo]}]
  {:query [{:new-todo (prim/get-query NewTodoItem)}]
   :initial-state {:new-todo {}}}
  (ui-new-todo-item new-todo))

@mark340 ^

Thanks. I'm trying that now

I just booted a fresh fulcro template with lein. It seems the workspaces doesn't work when running it from the server. . The main.js seems to be loaded correctly, but the other resources are 404 even though they exist in the resources folder. -> 404 Not found

@timeyyy_da_man if you don’t need full stack cards, try instead

(make sure the workspaces build is running on shadow)

I want full stack cards 🙂

There is nothing preventing you from using full stack cards…it looks like the shadown-cljs resource path in the dev section might be wrong path @timeyyy_da_man

:workspaces {:target     nubank.workspaces.shadow-cljs.target
                       :ns-regexp  "-(test|ws)$"
                       :output-dir "resources/public/workspaces"
                       :asset-path "/workspaces"
                       :devtools   {:preloads           [fulcro.inspect.preload]
                                    :http-root          "resources/public"
                                    :http-port          8023
                                    :http-resource-root "."}

if that works let me know and I’ll fix the template

just get http root and asset path to align, and it’ll work

oh wait…

that’s not quite right 😕

:http-root "resources/public"

yeah, that

:asset-path "/workspaces"

btw you don't need to run a separate webserver for the workspaces stuff

its just serving files so if you have something serving resources/public already you can just use that

cool…I’ll tune that up

I didn’t know if it affected dev preloads

hmm?

guess that is just compile now that I think about it

I only mean the :http-root :http-port stuff. those servers ONLY serve static files. they don't do anything themselves

so any webserver will do

yeah, on careful thought that is obvious

I will be moving that config stuff soon to make things a bit cleaner I hope

I think when I initially set this up I thought maybe if you ran shadow-cljs watch workspaces it would only start that dev tool

but I’ve seen that it pretty much starts them all no matter what

http servers are always started as you may want to use them to test a release build

would suck if they only run with watch

AFAICT the only thing wrong is the resources/public/workspaces/index.html

<script src="/js/main.js" type="text/javascript"></script>

hmm no actually that is fine

(given the current generated default config)

@thheller /src/main/wslive/server_components/middleware.clj in the wslive function is what gets served when running from the backend server. @tony.kay PR sent

I already released a new template…was it still not right? @timeyyy_da_man

i didn't pull it yet, i will try it out

it says the last commit was 24 days ago?

mm ok, now i see the changes, github was a bit delayed.. will test

@timeyyy_da_man don’t bother…I’m testing.

it wasn’t right

README also needed an update in order for both to work with same build…with figwheel they were diff builds

in shadow they are the same, so inconsistencies mattered

re-pushed the new template…that should make it work for both…updated readme with instruction changes as well

quick question. I’ve created a custom remote with Pathom, etc per the example to execute a few rest calls. Everything works fine, but I need to grab a security token from an auth lib, I’ve stored in the app db, from ‘inside’ the resolver. Not sure of the best way to approach this, and wondering if this kind of stuff belongs there or just in local storage or something.

@timeyyy_da_man Thanks for checking

@eoliphant it’s fine to use app state from within a resolver, if you’ve put it in the env…or from anywhere for that matter. Saving off the reconciler to you can get app state for arbitrary uses is fine.

Ok, cool. I was having some weird problems accessing it When I say just referenced the app atom directly in the parser setup call Going to look at it again when I get home