Matcher works only after navigating to the same route at least once. | Angular Community | Page 1

vagrant crag Feb 27, 2023, 5:50 PM

#

We have a nested structure were we want to change the layout of the page based on a query param, so for this we have 2 components that will be displayed based on matcher , here is the stackblitz https://stackblitz.com/edit/angular-5bnobf?file=src%2Fapp%2Fmain%2Fmain%2Fmain.component.html,src%2Fapp%2Fmain%2Fmain%2Fmain.component.ts,src%2Fapp%2Fmain%2Fmain%2Fmain.component.css,src%2Fapp%2Fmain%2Fmain-routing.module.ts,src%2Fapp%2Flazy-loading%2Flazy-loading-routing.module.ts,src%2Fapp%2Flazy-loading%2Flazy-loading%2Flazy-loading.component.html,src%2Fapp%2Flazy-loading%2Flist%2Flist.component.ts,src%2Fapp%2Fmain%2Fmain.module.ts,src%2Fapp%2Ftab-1%2Ftab-1-routing.module.ts,src%2Fapp%2Ftab-1%2Ftab-1.module.ts,src%2Fapp%2Ftab-1%2Ftab-1%2Ftab-1.component.css,src%2Fapp%2Ftab-1%2Ftab-1%2Ftab-1.component.html

StackBlitz

Angular (forked) - StackBlitz

A angular-cli project based on @angular/animations, @angular/common, @angular/compiler, @angular/core, @angular/forms, @angular/platform-browser, @angular/platform-browser-dynamic, @angular/router, core-js, rxjs, tslib and zone.js.

#

Matcher works only after navigating to the same route at least once.

polar trail Feb 27, 2023, 6:17 PM

#

Why don't you simply assign a dumb component to your component-1 path, responsible of displaying grid or list based on the queryParams it receives?

vagrant crag Feb 27, 2023, 7:09 PM

#

Also Tab1Component can decide which component to be displayed based on queryParams but I want to find a better solution to this

#Matcher works only after navigating to the same route at least once.