This is great way of reading data from dynamic parameters and query parameters. Previously we had to subscribe in order to get the data. Love your content. Thank you Also i had taken up your ngrx course on udemy. But now i think we need a refresh of the same as we now have signal stores 😅😅
Extremely helpful video to understand routing in Angular, I watched 5 times. The only confusing me is router-outlet is a directive instead of a component?
Angular can infer queryParams for both module-based components and standalone components. The way queryParams are handled is independent of whether the component is part of a module or is a standalone component.
Yes. And additionally in this case it's just a plain component where router feeds params from either params, query or data. You can even use this comp without router.
@@MonsterlessonsAcademy Sorry I wasn't clear. Maybe this is a dumb question but the right-hand side of the equal sign is the same in these two lines, and yet pageId and limit are different: pageId = input.required(); limit = input.required(); How is this possible?
am getting this compilation issue while using redirectTo Type '(routes: any) => string' is not assignable to type 'string'. below is my code for it { path:'old-pages/:pageId', redirectTo: (routes)=>{ return `/pages/${routes.params['pageId']}`; }, },
I am not joking, this is the best angular tutorial video I have ever seen. Everything very clear and straight to the point
Glad you like it!
This is great way of reading data from dynamic parameters and query parameters. Previously we had to subscribe in order to get the data. Love your content. Thank you
Also i had taken up your ngrx course on udemy. But now i think we need a refresh of the same as we now have signal stores 😅😅
Glad it was helpful! Signal store is not global therefore we can't replace ngrx store with it. It is suitable for organazing local signals for comp.
You are the best!! I will buy one of these courses for sure!!
Glad you like my content!
Great video and very much helpful, Keep it up!
Will do
What an amazing video. Thank you very much i really learned alot!
Glad it was helpful!
Very helpful. Thanks!
Glad it was helpful!
Great video. Thanks so much :)
Glad it was helpful!
Very cool and nice content, for real!!! can you expecify the angular version in description ? TNX
You can check the attached source code and see the Angular version in package.json.
@@MonsterlessonsAcademy sorry mate i'm layzier than my routes
Extremely helpful video to understand routing in Angular, I watched 5 times. The only confusing me is router-outlet is a directive instead of a component?
Yes it's a directive
Amazing!!!
Thanks
amazing content
Glad to hear that!
19:44 I would like to see how to use async resolver to load data from the API, based on route paramater.
Amazing content! but i have a question.. In Angular 18, we use input to get parameters and we no longer need ActivatedRoute?
In most cases no
Could you share your vscode profile/config, looks nice
I covered it here ua-cam.com/video/lvKjSBbQXxs/v-deo.htmlsi=zHnipazX6VvJvO5E
can angular also infer the queryParams when the route component is a module? Or does this only work for standalone components?
Angular can infer queryParams for both module-based components and standalone components. The way queryParams are handled is independent of whether the component is part of a module or is a standalone component.
Yes. And additionally in this case it's just a plain component where router feeds params from either params, query or data. You can even use this comp without router.
How does the “input” signal return different values?
What do you means by return? Angular router passed properties from data, params and query params. If you have such input, you will get a value.
@@MonsterlessonsAcademy Sorry I wasn't clear. Maybe this is a dumb question but the right-hand side of the equal sign is the same in these two lines, and yet pageId and limit are different:
pageId = input.required();
limit = input.required();
How is this possible?
Great
Thanks
am getting this compilation issue while using redirectTo
Type '(routes: any) => string' is not assignable to type 'string'.
below is my code for it
{
path:'old-pages/:pageId',
redirectTo: (routes)=>{
return `/pages/${routes.params['pageId']}`;
},
},
Are you on the older Angular version? Then routerTo function doesn't exist.