hey @tony.kay, quick question. a follow on to my last, i have access to the reconciler in my resolver now, but I’m not clear on how to issue an arbitrary query. so that I can do something like (let [token (??? resolver [[:sec-token '_]])]?

@eoliphant get the state atom and do a get on that?

ah hell

lol

thanks 🙂

(prim/app-state reconciler) by the way 🙂

You can also issue queries using db->tree (https://github.com/fulcrologic/fulcro/blob/bae67e67abe1b15c74a10768be53c3d83fcdc411/src/main/fulcro/client/primitives.cljc#L1335) but getting the app state and working with it directly seems better for your use-case

yeah, for this at least, I know exactly what I want

are you running Pathom on the client by the way @eoliphant?

yeah, have a few unfortunate rest apis

we have to pull in

ah fair 🙂

this is actually inside the resolver for one of them

where we need to slap the security token on the api

it’s quite neat that you can wrap them in pathom resolvers and then have a nice interface for Fulcro to work with

yeah that’s a pretty killer feature

the ‘extra’ remotes

also note that you can also pass an atom to :initial-state when building the Fulcro client

so (I think) what you could have done is set up a state atom, pass it to initial state

yeah this is more of a pain

then just reference that atom in your resolvers

because, we have to handle the token possibly being refreshed etc

(but you would need to initialise that atom manually)

ah ok

i see what you’re saying

may try that on the next pass

By the way I am very much a beginner with Fulcro as well so don’t take anything I say as gospel 😛

i’m actually 50/50 about the suitability of keeping that token in the app db at all

since the security lib, we’re using already maintains it in local storage or something

I guess it’s fine in the app db if it doesn’t need to be persisted

if it does, local storage, although some people would argue that’s unsafe

(and that you should use cookies instead)

if it’s already in local storage, why put it in the app db though?

hey quick question Im seeing that (:state reconciler) gives me just the app db, and (prim/app-state reconciler) seems to return it plus a bunch of other stuff

yeah, that’s why I’m back and forth about it, probably needless complexity. Since the js lib, that handles this is already managing that

https://github.com/fulcrologic/fulcro/blob/develop/src/main/fulcro/client/primitives.cljc#L2438

I’m not sure what :state on the reconciler corresponds to

there’s other info, about the user that might be useful to stick in there, but the token itself, probably not so much so

but prim/app-state gets [:config :state]

in my application I am storing the security token in an https-only cookie. So I don’t have to care about it at all; it’s passed automatically with requests (and stored)

but for you that’s obviously not an option since you are working with an existing API

if there are no other factors at play I would just leave it in local storage and not pull it in the app db

seems unecessary

yeah that’s what I’m leaning towards

we’re using cljs-http which i like because it’s all core.async’y

but it doens’t seem to support interceptors, which would be nice

since we basically want to: add the token, try the request, if it 401's refresh the token, then retry etc. each time so looking into that as well, and as we talk about it more definitely going to just rip it out at this point lol

lol yeah. Well on my application I use the built-in http fulcro remote (since my API is fulcro-compatible). I added a middleware which looks for 401s and if so, refreshes the application (which redirects to the login page)

crude, but it works

I could have attempted to refreshed the token there as well

it’s odd cljs-http doesn’t support interceptors though. Surely you can add a “middleware” step somehow?

(I haven’t used it)

yeah i’ve been looking at it

would be a useful pr lol

@eoliphant are you writing a novel? 😄

hey I have a question. I have a requriment for some ‘dynamic’ forms. where as opposed to say this from the form state demo

(defsc PhoneForm [this {:keys [:db/id ::phone-type root/dropdown] :as props}]
  {:query       [:db/id ::phone-type ::phone-number
                 {[:root/dropdown '_] (prim/get-query bs/Dropdown)} ;reusable dropdown
                 fs/form-config-join]
   :form-fields #{::phone-number ::phone-type}
   :ident       [:phone/by-id :db/id]}
  (dom/div :.form
    (input-with-label this ::phone-number "Phone:" "10-digit phone number is required.")
    (input-with-label this ::phone-type "Type:" ""
...

{:form/name ..
 :form/id :phone/id
 :fields [{:key :phone/number :type :text :validations [....]} ...] 

lol I’d started typing this, then had a person in my office like every 5 mins lol

what would be the ident for this? I’m getting a warning I need one

(defsc FormProto [this {:keys [which-tab]}]
  {:query [:which-tab]
   :initial-state {:which-tab :form-proto}}
  (dom/div "FormProto"))

@njj are you using that inside a router?

if not, you can make an ident up

something like :ident (fn [] [:COMPONENT/by-id ::form-proto]) would work