Angular Router Navigate re initializes component
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am navigating from component A to component B using router.navigate with query param. And navigating back from B to A using router.navigate with exact same query param.
1). Is it expected behavior that component A is initialized with new instance when redirected to, from component B?
2). I don't want to reinitialize component A and use that same instance of A. How can I achieve this.
I am using Angular 6
angular navigation router asked Nov 29 '18 at 3:54
Kalyani ShirwalkarKalyani Shirwalkar
225
add a comment |
I am navigating from component A to component B using router.navigate with query param. And navigating back from B to A using router.navigate with exact same query param.
1). Is it expected behavior that component A is initialized with new instance when redirected to, from component B?
2). I don't want to reinitialize component A and use that same instance of A. How can I achieve this.
I am using Angular 6
angular navigation router asked Nov 29 '18 at 3:54
Kalyani ShirwalkarKalyani Shirwalkar
225
Yes it is expected, when you navigate from CompA to CompB, do you want the CompA to be visible?
– xyz
Nov 29 '18 at 3:59
add a comment |
I am navigating from component A to component B using router.navigate with query param. And navigating back from B to A using router.navigate with exact same query param.
1). Is it expected behavior that component A is initialized with new instance when redirected to, from component B?
2). I don't want to reinitialize component A and use that same instance of A. How can I achieve this.
I am using Angular 6
angular navigation router asked Nov 29 '18 at 3:54
Kalyani ShirwalkarKalyani Shirwalkar
225
I am navigating from component A to component B using router.navigate with query param. And navigating back from B to A using router.navigate with exact same query param.
1). Is it expected behavior that component A is initialized with new instance when redirected to, from component B?
2). I don't want to reinitialize component A and use that same instance of A. How can I achieve this.
I am using Angular 6
angular navigation router angular navigation router asked Nov 29 '18 at 3:54
Kalyani ShirwalkarKalyani Shirwalkar
225
asked Nov 29 '18 at 3:54
Kalyani ShirwalkarKalyani Shirwalkar
225
asked Nov 29 '18 at 3:54
Kalyani ShirwalkarKalyani Shirwalkar
225
asked Nov 29 '18 at 3:54
Kalyani ShirwalkarKalyani Shirwalkar
225
asked Nov 29 '18 at 3:54
Kalyani ShirwalkarKalyani Shirwalkar
225
225
Yes it is expected, when you navigate from CompA to CompB, do you want the CompA to be visible?
– xyz
Nov 29 '18 at 3:59
add a comment |
Yes it is expected, when you navigate from CompA to CompB, do you want the CompA to be visible?
– xyz
Nov 29 '18 at 3:59
Yes it is expected, when you navigate from CompA to CompB, do you want the CompA to be visible?
– xyz
Nov 29 '18 at 3:59
Yes it is expected, when you navigate from CompA to CompB, do you want the CompA to be visible?
– xyz
Nov 29 '18 at 3:59
add a comment |
1 Answer
1
active
oldest
votes
You can possibly prevent components from being destroyed on navigating to a different URL, refer the documentation here.
answered Nov 29 '18 at 4:09
Akash SrivastavAkash Srivastav
16110
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53531604%2fangular-router-navigate-re-initializes-component%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can possibly prevent components from being destroyed on navigating to a different URL, refer the documentation here.
answered Nov 29 '18 at 4:09
Akash SrivastavAkash Srivastav
16110
add a comment |
You can possibly prevent components from being destroyed on navigating to a different URL, refer the documentation here.
answered Nov 29 '18 at 4:09
Akash SrivastavAkash Srivastav
16110
add a comment |
You can possibly prevent components from being destroyed on navigating to a different URL, refer the documentation here.
answered Nov 29 '18 at 4:09
Akash SrivastavAkash Srivastav
16110
You can possibly prevent components from being destroyed on navigating to a different URL, refer the documentation here.
answered Nov 29 '18 at 4:09
Akash SrivastavAkash Srivastav
16110
answered Nov 29 '18 at 4:09
Akash SrivastavAkash Srivastav
16110
answered Nov 29 '18 at 4:09
Akash SrivastavAkash Srivastav
16110
answered Nov 29 '18 at 4:09
Akash SrivastavAkash Srivastav
16110
16110
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53531604%2fangular-router-navigate-re-initializes-component%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Yes it is expected, when you navigate from CompA to CompB, do you want the CompA to be visible?
– xyz
Nov 29 '18 at 3:59