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.
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
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).
it is nil nil and not some-entity/id nil because the union component supports different entity types
so the ident is defined as (defn [] [type id])
Upgraded to latest 3.4.22. Same message.
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?
can you share a gist of the relevant code?