Is there any support for a URL such as user/id/products with the dynamic routing?

@pvillegas12 of course…do the docs not make it clear?

trying to get it to work right now

using #(dr/change-route-relative this UserDetails ["products"]) but in the will-enter I’m not receiving the user id

tried doing (dr/change-route this ["user" id "products"]) too

But it chops off products in this case for some reason (loooking at the fulcro db for routing)

Fulcro 2.8.3 on Clojars, and Incubator 0.0.29. The Fulcro fix is a long-overdue fix to fulcro logging. The incubator fix adds debug logging (which requires 2.8.3 of Fulcro) to state machines so you can see how they are working. Incubator also has deferred routing fixes for dynamic routing. See the docs, as the API had to include a new method to accomplish it properly.

@pvillegas12 what is your prefix defined as for the route target?

:route-segment (fn [] ["user" :user-id])

ok, so that one can consume /user/222

right

then you have a nested router underneath there?

correct

with prefix [“products”]

yup

the route params are the ones I’m not receiving

I don’t think I’ve tried that particular combo, but I expect it to work

should I upgrade to the latest fulcro?

the upgrades don’t affect this for sure

ok

well, depending on your deferral of routing

You may have discovered another bug….darn-it, I just finished fixing the last one you found 😉

should I be doing the dr/change-route-relative or dr/change-route?

😄

depends on what you pass

both should work right?

right, but arguments have to vary properly

either ["user" id "products"] or simply ["products"] with the right prefix class

the latter should work if you pass the router whose targets include one that accepts “products”, yes

The former would have to be sent to the router that targets the prefix target accepting “user”

Technically it should work if passed something “in between” the two as well

I have to go to dinner…back later

If you upgrade to the latest versions, you’ll be able to see a LOT more info with debug logging in console

it’ll tell you what’s going on in the state machines,e tc.

I’ll do that right now

After updating getting more debugging info, looks like it does the RootRouter transition but

Attempt to get an ASM path [:fulcro.incubator.ui-state-machines/local-storage :pending-path-segment] for a state machine that is not in Fulcro state. ASM ID:  :dataico.ui.user.details/UserRouter

you upgraded incubator as well?

that warning should no longer be there

I’m done for tonight…basically when you route it calls begin on the state machine it matches. Perhaps for some reason it isn’t ok with the id-based target

thanks for looking into it 🙂

I may have time to look at it more tomorrow. The source isn’t that large if you wanted to clone incubator and do deps :local/root and debug it further

in https://wilkerlucio.github.io/pathom/#_parameters queries like:

[(::instruments {:sort :instrument/brand})]
  

(defsc  MyComp [this props]
  {:query ['(::instruments {:sort :instrument/brand})]}
  )
  

ah - probably because I have a {:all-instruments (prim/getQuery MyComp)} in my root - not sure how to avoid that

because if I remove :all-instruments in my root query - how do I: :started-callback (fn [dashboard] (df/load dashboard :all-instruments MyComp))?

@nha I think it's just a matter of using one or the other consistently

@nha if you component has an ident, you can use the ident instead of a keyword to load a specific instance.

but if you intend to load “many” like your q implies, then why wouldn’t you want that join?

remember docker additions changed db configs a bit

just merged to develop

@tony.kay got the routing working finally, traced down the bug in my code 🙂

I have the following routing structure

CompanyDetails [:company/by-id :company-id]
|                           \
UserDashboard                InvoiceDashboard

UserDashboard and InvoiceDashboard are defined in the CompanyRouter, not the RootRouter as CompanyDetails, so I don’t have access to the router param for the :company-id

@pvillegas12 you mean you want to use the current route to figure out the new one?

1 - Use relative routing to avoid needing to know it 2 - Read the current route and pull it out of the path segments 3 - Remember the value in a well-known location in app state and use abs change route (e.g. when you originally set the route, remember it)

@pvillegas12 Incubator 0.0.30 is on clojars, and includes computed props proxying through the router.