@njustice does that mean that was your problem?
I’ve republished the book with more of the unnecessary transaction quoting removed. The book still talks about the fact that you can quote, but that it is usually not necessary.
I actually need to update the text…it does have some misinformation inherited from 2
I’m on Fulcro 2, I ended up just flattening the data a bit and making the field value part of the parent form - removing the subform all together
Also yes the field name from the db is value lol
ok, fixed a bit more
so, all you needed to do was add a refresh to the transaction (a keyword in the parent’s query)
it’s a data-driven refresh model. F3 switched to not needing that as much, but you just tell it a keyword in the parent query to get the parent to refresh
(transact! this [… :parent/key])
will do it on transactions
I really recommend moving to F3 if you can…so many nicer things there
Hey @tony.kay , I noticed, that some of my dynamic-query ids have a superfluous :
as the first symbol, while others doesn’t.
This leads to registry-key->class
returning nil
for these entries.
Do you have an idea what is causing this?
The query-ids in question are all of components that are targets in a nested dynamic router.
Ok. Another hint. All components that have the `:` are using hooks
Yes. the :queryid of components using hooks are always starting with :
while “normal” components do not.
Seems like for non-hook components the :displayName ist build with (str/join "/" [(namespace fqkw) (name fqkw)])
while for hooks it is just the key it is just str