Type of Change
Summary
As detailed in , marking visitor pattern functions as async was leading to intermittent failures in the compiler due to nested components not being defined in time before the parent was serialized.
However, it would be nice to solve this!
Details
Definitely more than just marking them as async again, but I could see at very least being able to parallelize siblings? So for instance, something like this
<x-header></x-header>
<x-footer></x-footer>
Should be able to support parallel rendering paths. This might require an initial reading of the DOM but could definitely make things faster where possible.
Type of Change
Summary
As detailed in , marking visitor pattern functions as
asyncwas leading to intermittent failures in the compiler due to nested components not being defined in time before the parent was serialized.However, it would be nice to solve this!
Details
Definitely more than just marking them as
asyncagain, but I could see at very least being able to parallelize siblings? So for instance, something like thisShould be able to support parallel rendering paths. This might require an initial reading of the DOM but could definitely make things faster where possible.