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
{{ message }}
This repository has been archived by the owner on Sep 19, 2024. It is now read-only.
Hi all
I am new to Angular ( working on Angular 5 )
I found this great module and it fits my needs.
I manage to make it work fine if I place the code in my main component
Ex :
App - component home
App - component login
App - component password
but it is kind of tedious and from what the team is planning there will be lots of main components.
So I thought of adding a child component ( like footer/header etc ) and created an idle child component that I placed on all my templates.
My issue is that it triggers on the first page load, but once I start navigating to other routes, the component does not trigger itself or does not reset itself. Tough for me to say for sure.
Is there a way to create an idle component that I could reuse in all my other main components?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi all
I am new to Angular ( working on Angular 5 )
I found this great module and it fits my needs.
I manage to make it work fine if I place the code in my main component
Ex :
App - component home
App - component login
App - component password
but it is kind of tedious and from what the team is planning there will be lots of main components.
So I thought of adding a child component ( like footer/header etc ) and created an idle child component that I placed on all my templates.
My issue is that it triggers on the first page load, but once I start navigating to other routes, the component does not trigger itself or does not reset itself. Tough for me to say for sure.
Is there a way to create an idle component that I could reuse in all my other main components?
The text was updated successfully, but these errors were encountered: