fulcro

Book: http://book.fulcrologic.com, Community Resources: https://fulcro-community.github.io/, RAD book at http://book.fulcrologic.com/RAD.html
Jakub Holý 2021-05-27T07:46:03.045300Z

It is harder to learner also because it covers more and does more. Helix is trivial - but it has only UI, no idea of data and remote access. But you are right, materials are a part of it.

Jakub Holý 2021-05-27T07:55:35.045500Z

I guess the props passed to the component are nil , no? Is that expected or a mistake? Does it make sense to render the component without any data? If it does then either ignore the warning or use :initial-state {} (+ propagating it all the way up) to make sure there are non-nil props. But given then this ident seems dynamic, i.e. props-dependent, why would you render the component when it has no props? What surprises me is [nil nil] , should it not be [:some-entity-name/id nil] ? Also, do you have latest Fulcro? I would expect some of the warnings inside it to be triggered?! See https://github.com/fulcrologic/fulcro/blob/develop/src/main/com/fulcrologic/fulcro/components.cljc#L630

Marcus 2021-05-27T08:44:45.045800Z

Hi! I will check. The problem is that this is a union. Initial state is calculated from the child component and thus should always pass on values to use as the ident.. (as I understand it).

Marcus 2021-05-27T08:46:14.046Z

it is nil nil and not some-entity/id nil because the union component supports different entity types

Marcus 2021-05-27T08:46:37.046200Z

so the ident is defined as (defn []  [type id])

Marcus 2021-05-27T10:30:22.046400Z

Upgraded to latest 3.4.22. Same message.

Jakub Holý 2021-05-27T12:13:24.046600Z

I am not familiar with unions. But it still looks like initial state issue to me (and you can check that by looking into the client db). Also, why is type nil? That should likely not happen?

Jakub Holý 2021-05-27T12:20:36.046800Z

can you share a gist of the relevant code?