It would be nice to have a recap screen at the end of each video with a bullet list of things you have learnt, for example this video would be like: - Can define different indipendent routing using "name" attribute on the router outlet and the "outlet" property on our route configuration; - Use empty string and "outlets" property in Link Param Array to navigate to a named router outlet; - Router outlet has active and deactive events you can use to show/hide controls to the user.
Great content! You talk with great interest so that we cannot stop watching the video. Thanks for the new videos! By the way, the idea of implementing a drag&drop in the application is actual. So, I would be glad to see it :)
Thanks for your example, it is very nice and shows basically all of the elements one would need. I personally had the problem that I've tried to place the named outlet inside of a component that would be loaded by the "primary" (unnamed) outlet. This didn't work so after realizing I would need them in parallel it's working properly.
Wow! I'm thrilled by the explanation of these topics, it was simple and precise. I guess this is similar to what udemy is using to display content along side their Q/A (though it was react), if I'm wrong. I will definitely implement this on the project I'm working on. Thanks
ur video is impresive but i really hope u will have course that explain angular from very start to very end one day. but anyway, thanks for your skill sharing
Hey Dmytro! Amazing explainantion!! Thanks for introducing this to us. Also could you please additionally show us that drag of image functionality to this project?
Can you make an example with lazy loading modules where outlet definitions are setup in the lazy loaded routing module. I can't figure out how it works! Seems not that easy...........
I'm just getting into Angular. I feel like the community for Angular is not as large as that for ReactJS, so channels like this one of Mr. Dmytro should be much more recognised. Just subscribed 😄Hope to see more content from you. Well done!
Hey, I would find it awesome if you showed what you were going to show at the beginning of the video. Then we go through the video with some kind of idea of what the intent is.
Im currently learning Angular and in a project of mine i came across this specific Routing task. Its a chatapp where i also want to have multiple outlets on a desktop view (sidenav, main chat window, thread chat window). I figured to implement the routing the same way you showed in this video, but wondered how i would switch between different Routings in different screen resolutions. E.g. in the mobile view every components gets rendered in the same outlet because the should only be 1 component visible at a time, but on a desktop the routes should "fork" like you showed. I implemented a service to navigate between different urls, where the service checks the windowsize and either sets the "normal" url or the (outlet: {'url'}). My only problem here is the part with the restoreability. When im on the desktop view and having the (outlet: {'url'}) url and resizing the page at runtime into the mobile resolution, the url of course doesnt update so the mobile view cant get rendered because the routes array doesnt contain a route to the named outlet. Just on reloading the page with an empty route and navigate back to the chat works. Can you maybe help me with this issue?
Hey Dmytro, nice video about named routes! I remember using them and they were called auxiliary routes same time ago. Where they renamed to named routes? Also I used them to implement a drawer that was synchronized with the url which is nice when you want to be able to navigate back and forth in drawer with browser history.
Hey Alex! Yeah, I also remember it was named auxiliary routes but in docs, they are known as "named outlets" but I have no idea when and why it happened :) Anyway, thanks for the comment and the use-case you shared with us!
You're making very useful videos, Dmytro, thank you! I just have one idea for further themes - unit testing of components, especially with routerLinks, from first glance not a very trivial thing
Cool explanation. But I am sure there are some more complex use cases, will be nice to see them also. For example if we can have outlet with multiple children, or with lazy load modules. As well if is possible to have several named outlets. For example I have issue to define named outlets in app routing but html tag in a lazy load modules. I assume it is not possible but hope there is some option to do that. Thanks. I really love and appreciate your courses! Have a good time.
Hey there, thanks for sharing that. It was really useful and it makes the router-outlet function more flexible. However, I have a question. It seems that with this layout, the combination of URLs must inevitably be done in a "specified way" for it to work. If the project is designed for use by a specific system, it doesn't seem like a problem, but if the project has SEO requirements, I'm worried that this combination of URLs might not be very SEO-friendly. Is that the case, or am I just worrying too much?
Hi Thanks for introducing this to us. can u also tell me what the name of extension of visual studio code check for package size for Ex.: 110.4K (gzipped: 35K) plz what extn. name its also helpfull 110.4K (gzipped: 35K)
Hi, I have done what you have mentioned in this video. When I deployed this to Azure it works fine but when I try to enter the url directly and press enter, page never loads. Application unable to find it. What is the solution of this please.
@@DecodedFrontend awesome, just it would be good if you share little contents and posts there, you know in youtube it is not so convenient))) Good luck man, u r doing amazing job :)
It was very useful. I would like to know if there is some way to escape from the ../(detail:extra) suffix when you have another link in the DOM as it's mentioned in this bug: github.com/angular/angular/issues/15338 or if it's something that wasn't already be fixed. Thanks!
