You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the helper is used in a route template that is rendered into a liquid-outlet, two templates are rendered at the same time during a transition. One of these templates inevitably does not match the currently active route hierarchy. If this template then expects a certain task to be resolvable, the assertion fails.
Somehow this only started occurring in Ember 3.13.x. in our app, but I don't want to waste time digging deeper.
IMO usage of this addon should be discouraged anyway. I believe route tasks should be returned as part of the model, like so:
When the helper is used in a route template that is rendered into a
liquid-outlet
, two templates are rendered at the same time during a transition. One of these templates inevitably does not match the currently active route hierarchy. If this template then expects a certain task to be resolvable, the assertion fails.Somehow this only started occurring in Ember 3.13.x. in our app, but I don't want to waste time digging deeper.
IMO usage of this addon should be discouraged anyway. I believe route tasks should be returned as part of the model, like so:
The text was updated successfully, but these errors were encountered: