I added a new component into an existing hierarchy like

A -> B -> C

A -> b' -> B -> C

I’m also not confident I’m storing a list of items correctly. I have the list at [:component/id ::ListComponent :root/list]

I’m even more confused because I manually added the missing edge in the repl (or so I thought) and it’s not registering through the router.

So, I managed to resolve the issue, although I’m not totally clear on how this worked. I added :initial-state options down the tree to the components I was trying to manually add, and then since they existed in the graph, everything was traversable.

most problems for beginners are making sure there is initial data in the db, which is always just that: Have an initial-state declaration on your components so that Fulcro can put them in your DB for you. If you don't list those, Fulcro expects you'll put them there some other way (e.g. loads)...which is then up to you during initialization

This https://blog.jakubholy.net/2020/fulcro-divergent-ui-data/#_inserting_a_stateful_ui_component_between_a_parent_child_entities might clarify And as https://fulcro-community.github.io/guides/tutorial-minimalist-fulcro/index.html#_components_initial_state states: > :initial-state ... to establish links (edges) between (typically singleton) components / data entities in the client DB.

Probably should be considered a bug. It isn't technically the same route because the parameters are different, but because you are not exiting and re-entering the route the state machine won't be told.

betting it works fine if you go out and back in...so, you CAN manually call the code that the route event calls: form/start-form!, though you should probably also call the code that stops the old one. The real solution is for the routing to actually cause the exit/enter events itself 😄

See also form-will-leave and form-will-enter...that's the pair that normally runs from the router events

The use-case in your example is kind of a corner that almost no one will hit...when do you do explicit entity routing like that...it was just a dumb example to show the methods could be called.

Mostly you'll go back to a report that lists them and pick a diff one, which will exit/enter and not cause issue

Thanks so much the hints here, @U0CKQ19AQ — Just to make sure I’m tracking: AccountInvoices is a report, not a form, correct? Do I still need to call form/start-form!? (Still hacking away on this, determined to get this to work. 🙂 And yes, a workaround is just to call another conventional report, which is “fine”. 🙂

I actually thought this would work, but it didn’t:

(report/report-will-enter this {:account/id (new-uuid 101)} AccountInvoices)
(rroute/route-to! this AccountInvoices {:account/id (new-uuid 101)}))

ah right...report...same exercise. Look at the report ns for the helpers

route-to won't do anything because you're already there

but will-enter logic should do it

report has start-report!

Thx — will look at again later today!