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
As mentioned above you need to add the {{head-layout}} component once and only once in an application wide template
But I'm finding that I need to include {{head-layout}} at whichever route level I interact with the headData service in order for it to work with FastBoot.
For example, if I have /profiles/1 which corresponds to an application route and a profile show route, both of which set data on the headData service, then I will need {{head-layout}} in application.hbs as well as profiles/show.hbs in order for the changes in the profile show route to be reflected after FastBoot render.
Hope that makes sense.
The text was updated successfully, but these errors were encountered:
@mhluska The problem here is Fastboot does not include prototype extensions. This is probably an issue for quite a few apps that access firstObject in the template when they expect it to be there.
The readme says:
But I'm finding that I need to include
{{head-layout}}
at whichever route level I interact with the headData service in order for it to work with FastBoot.For example, if I have
/profiles/1
which corresponds to an application route and a profile show route, both of which set data on the headData service, then I will need{{head-layout}}
inapplication.hbs
as well asprofiles/show.hbs
in order for the changes in the profile show route to be reflected after FastBoot render.Hope that makes sense.
The text was updated successfully, but these errors were encountered: