Tomas Rimkus
Tomas Rimkus
@jamesdaniels not sure I understand what you mean by "don't need to be called". In angularfire v6, you had to add those services to the app providers. Isn't that the...
@jamesdaniels Minor nitpicking: - instead of creating multiple subscriptions with `async` pipe, you could use [`*ngrxLet`](https://ngrx.io/guide/component/let) to resolve the observable or [`@ngneat/until-destroy`](https://github.com/ngneat/until-destroy) to automatically unsubscribe when component is destroyed. -...
No, I am not using header and footer. Negative margin workaround works for me.
I can do it.
Unfortunately, the simple trick with negative margins doesn't work because of the scrollbar:  Feel free to look into this when you have some time.
That's ok, it's not a major issue.
> Do you know how CloudRun works? That is really what I was trying to fix. There I do not have control over the version. Since I got the same...
Why not just use [@ngneat/error-tailor](https://github.com/ngneat/error-tailor/) and avoid the `tui-error` boilerplate altogether?
As a workaround until this is fixed you can add the following line before calling `tourService.initialize()`: ```ts (this.tourService as any)['subscribeToNavigationStartEvent'] = () => {}; ```
Fixed in `v12.0.3`.