Is that sort of going against the intent of mercury components by subscribing to a child component state value and piping new values to another child component state? If so, is it necessary in this context? I thought it would work without this line because both components and their values are all nested into mercury.structs, which should kick off the top-down rendering anyway.
I was reading the mercury components doc and studying the black box aspect and how events are published for the parent to hook into.
Then I came across this line in the markdown demo:
Is that sort of going against the intent of mercury components by subscribing to a child component state value and piping new values to another child component state? If so, is it necessary in this context? I thought it would work without this line because both components and their values are all nested into mercury.structs, which should kick off the top-down rendering anyway.