Targets must have a query. I do not think [] is enough, change it to ['*] . See point 1. under Example 1 under https://fulcro-community.github.io/guides/tutorial-advanced-minimalist-fulcro/#_the_bare_essentials_of_fulcro_routing

Also see the comment about :initial vs nil at point 2. under Example 4.

When you reload the page, the route starts as unrouted (= nil) before the change-route! kick is (which I assume your (history/dispatch-current!) calls). To deal with that you can tell the UI not to display until the state has settled down. Here https://github.com/holyjak/minimalist-fulcro-template-backendless/blob/example/routing+pre-merge/src/com/example/ui.cljs I do that by using the flag :ui/ready? which I only set to true after my ui is ready (here after the data is loaded, in your case you could transact it right after you call dispatch-current) > and after the text `Home` of the component. In fact, `current-state` of the `Router` is always nil in this case Does it mean your routing does not work and the router is simply displaying the default = first target? Notice that when the state is :routed then the body of the router is not executed so you would not see the state printed. Thus it is to be expected that the only state you see printed is the initial nil (after which it presumably goes right into :routed and displaying Home) What does the DB contain? What does the Transactions tab show? Is everything there as you expect?

Thanks @U0522TWDA to answer me 🙂 > Does it mean your routing does not work and the router is simply displaying the default = first target? I think the router works because when I reload the page on /foo the router display correctly No route selected For the moment I have no DB and no transactions. I will check all your advices.

When I speak about DB and Transactions, I speak about the tabs of Fulcro Inspect

A possibly better alternative to using :ui/ready? is what is shown in https://book.fulcrologic.com/#_setting_the_route_early in the second code block, checking the router's state for :initial or nil and displaying "loading..." instead

If you haven't, I would highly recommend going through https://github.com/holyjak/fulcro-intro-wshop to get familiar with Fulcro Inspect and troubleshooting fulcro apps

FYI the updated https://fulcro-community.github.io/guides/tutorial-advanced-minimalist-fulcro/#_the_bare_essentials_of_fulcro_routing Example 2, point 8 now shows how to wait until the route is ready

Thanks you very much @U0522TWDA I will take a look

Not as far as I know. Personally, I would prefer to keep the site effect outside of rendering, ie there where the change enters the system (eg an onChange handler or a load's post mutation). You could store the value eg in an atom and just change a flag in the the client DB (eg :ui/external-data-version) to trigger Re-rendering of the component that needs to read the atom

Thanks. I'll tinker with it some more

“where a prop change”…what causes the prop to change? That’s where the logic belongs IMO

I think you will find the master-detail example from the RAD demo repo helpful: https://github.com/fulcrologic/fulcro-rad-demo/blob/1ba6973b2a461f2db9d75d7ab0f529432177d278/src/shared/com/example/ui/master_detail.cljc#L54 The state machine is just a map, so you can disable anything you want by assoc'ing in a different handler function to any event you want handled differently. You could copy/paste the existing handler and remove the lines you don't like, if that's what you need. I don't know if there's a cleaner way to do it.

THis commonly happens when a user has a form open and the entity gets deleted in the mean-time. When the user hits refresh, form will try to load the entity, get nothing from remote and open an empty form. Due to required fields being invalid now, the user cannot navigate from this form and they are stuck.