Nested components are initialised in the wrong order #97
Labels
accepted
This will be worked on
breaking
Introduces or requests a breaking change.
domain: Rust
Involves Rust code.
effort: 2
Relative effort required. There's no specific unit of measurement.
good first issue
Good for newcomers
type: bug
Something isn't working as expected
work: clear
A known solution is (to be) implemented.
Given a component
, Asteracea will currently evaluate this in the order
b - B - a - A
, which may be unexpected.It should be
a - A - b - B
, consistent with render-time evaluation. This can likely be achieved by (re-)parsing the container's binding earlier incomponent.rs
(where child components are implemented), before parsing its content.Sibling expressions should always run from top to bottom.
A test for both is necessary. Asserting and incrementing a counter in the relevant places should work there.
The text was updated successfully, but these errors were encountered: