This is cool video, but I don't like that there is no way to explicitly tell that this is not input but route params, wouldn't it be much better to implement this feature with separate decorator like @RouteParam() or add additional property to input decorator object (for example routeParam) like we have with required, transform and alias
Thank you. The down side of a resolver is that it blocks the navigation until the data is resolved. This has more info: angular.schule/blog/2019-07-resolvers
Thanks for the explaination. Could you please make a video concerning form management with @Input and Signals? I've noticed that signals and forms do not fit well, mostly if the signal must be used to fullfill the form and the same data must be used to perform a submit.
Glad it was useful! The signals features are not yet complete, including using them with @Input, with two-way binding, and with forms. These are features the team is still working on. I'll be sure to do some videos as soon as those features are available.
Nice Explanations like always thanks!!! still have a small question: i have for example a search input above the product details, where i can look directly for ids of products. Imagine i looked at product 5 at first load from the component, so id:5 is in the url. but then i want to see product 10. i write 10 in my input field, on submit i load right product, but writing new id in the url did not happened. is there a new way to update that parameter? or do i need to continue injecting the router and replace more or less with navigateByUrl? hope you have an alternative way ^^ thx thank you for your help
Yep, you are correct. I hadn't seen the new `numberAttribute` and `booleanAttribute` when I did this video. I've since put all of the above in this video: th-cam.com/video/5_YZVF0OAu0/w-d-xo.html Thank you!
If the id is not specified in the route can we use the Input to read the url param.. for example ?id=2&name=something . Will angular know to map these to id and name inputs automatically?
Thank you for the feedback. Yeah, I contemplated whether I should cover the "how routing works" to clarify how/where these parameters are set. Maybe that should have been its own video so the majority that already know that could skip that part?
@@deborah_kurata To be honest, we already have a lot of TH-cam channels explaining everything really fast. I like that Deborah explains slowly and takes time to speak about small important details like in this video. But, we know how it is, it's impossible to please everybody.
Out of curiosity ... is this comment because you personally use dark and this doesn't? Or is it because it is really too hard to read/see with the light theme? I ask because I know most developers use dark. But we've been told by most conferences and companies such as Pluralsight to always use light when recording videos because they are easier to see ... especially on smaller devices. Thanks!
@@deborah_kurata Hey deborah, your video was insightful, I didn't mean to disrespect. For me, it's mainly personal, I use dark themes everywhere. But it is also an issue if I'm scrolling at 11 or 12 PM through TH-cam, and the video makes my eyes bleed. Kind of hard to watch as you said. Cheers
Debora, thanks a lot! I wish I could explain things as you do. Thanks for doing such amazing videos!
That is kind of you to say. Glad you like them!
Amazing video as always, I especially liked the little addition of the explanation about deep linking
Glad you liked it! Thank you!
Thanks a lot for this ... Really loved the way you explain the concepts ... Just wow !!! 🤩
So nice of you to say. Thank you! 😊
Thank you !
Very good job, your channel deserves more subscribers
Thank you for watching!
And yes! 😊
I simply loved this explanation
Thank you!
great explanation, angular looks easy when you explain it
That is kind of you to say! Thanks! 😊
Wonderful!! I always thought that the snapshot.params way was too clunky. Thanks again Deborah. Amazing teaching
Glad it was helpful! 😊
Just wanna say that your tutorials are on point🔥.Thanks for the great content!
Thank you so much!
I love your stuff. Really great Job Deborah🔥
Great to hear! Thank you! 😊
amazing tips! thank you so much. 💕
Glad it was helpful!
This is cool video, but I don't like that there is no way to explicitly tell that this is not input but route params, wouldn't it be much better to implement this feature with separate decorator like @RouteParam() or add additional property to input decorator object (for example routeParam) like we have with required, transform and alias
very nifty and handy....thank you
Great to hear it was useful!
simple to the point explanation, recently subscribe and loved your content. 🔥
Thank you so much! 😊
amazing Job. thanks you from Germany!
Thank you very much! 😊
Thank you very much!😄
You're welcome 😊
Great! Thank you!
Thanks for watching!
Great video! Just little bit curious, is it better to use Resolver to reload data?
Thank you.
The down side of a resolver is that it blocks the navigation until the data is resolved. This has more info: angular.schule/blog/2019-07-resolvers
Great thank you mam providing great content 🙂
Thank you for watching! 😊
Amazing feature
Yes! I've been using it regularly now for my route parameters.
Hi Deborah, tanks for the video, does exist any difference from Input Binding for parameters and input binding for communication between components?
I'm not sure I understand the context of the question. A difference in what way?
Thank you 🎉
Cool!
Thanks for the explaination.
Could you please make a video concerning form management with @Input and Signals? I've noticed that signals and forms do not fit well, mostly if the signal must be used to fullfill the form and the same data must be used to perform a submit.
Glad it was useful!
The signals features are not yet complete, including using them with @Input, with two-way binding, and with forms. These are features the team is still working on.
I'll be sure to do some videos as soon as those features are available.
Nice Explanations like always thanks!!!
still have a small question:
i have for example a search input above the product details, where i can look directly for ids of products.
Imagine i looked at product 5 at first load from the component, so id:5 is in the url. but then i want to see product 10. i write 10 in my input field, on submit i load right product, but writing new id in the url did not happened.
is there a new way to update that parameter? or do i need to continue injecting the router and replace more or less with navigateByUrl? hope you have an alternative way ^^ thx
thank you for your help
Thank you!
I *think* I understand what you are asking? Any way you could create a little Stackblitz example?
@@deborah_kurata seems like everytime i post the stackblitz link, my comment is removed.... where can i send it to you? thanks
My apologies ... I didn't see your reply until now. What social media are you on? You can send it via one of those if you're still interested.
7:07 Can you use input transform instead of casting to a Number? Like so:
@Input({ transform: numberAttribute }) id = '';
It's a function. @Input({transform: (id) => Number(id)}) id = 0;
Yes! And it looks like @EmilioDegiovanni provided the syntax below. (I was planning on covering that in a separate, upcoming video. :-))
Thank you for providing the correct syntax!
@@deborah_kurata Angular 16.1 actually exposes numberAttribute and booleanAttribute coercion functions to handle this
Yep, you are correct. I hadn't seen the new `numberAttribute` and `booleanAttribute` when I did this video. I've since put all of the above in this video: th-cam.com/video/5_YZVF0OAu0/w-d-xo.html
Thank you!
If the id is not specified in the route can we use the Input to read the url param.. for example ?id=2&name=something . Will angular know to map these to id and name inputs automatically?
I'm on pto this week. I'll try it when I get back to the office.
can i access parent route params by this approach
Would this work in a route resolver
is it possible to do the same with the new signal input function?
Yes, it should work. Are you having issues getting it to work?
We love your videos deborah ❤️ but please try to come to the point faster. this video could be 3 min long and still explain the new content in detail
Thank you for the feedback. Yeah, I contemplated whether I should cover the "how routing works" to clarify how/where these parameters are set. Maybe that should have been its own video so the majority that already know that could skip that part?
@@deborah_kurata To be honest, we already have a lot of TH-cam channels explaining everything really fast. I like that Deborah explains slowly and takes time to speak about small important details like in this video. But, we know how it is, it's impossible to please everybody.
@@ErickCcsVzla Thank you! 😊😊
can u share the code please
You can find it here: github.com/DeborahK/Angular-TH-cam/tree/main/input-route-parameters
awesome video! Watched from freecode and again here on yt, if I could hit the like button 1000 times I would, tks a lot!
Thank you so much!
Oh my lord light theme
Out of curiosity ... is this comment because you personally use dark and this doesn't? Or is it because it is really too hard to read/see with the light theme?
I ask because I know most developers use dark. But we've been told by most conferences and companies such as Pluralsight to always use light when recording videos because they are easier to see ... especially on smaller devices.
Thanks!
@@deborah_kurata Hey deborah, your video was insightful, I didn't mean to disrespect. For me, it's mainly personal, I use dark themes everywhere. But it is also an issue if I'm scrolling at 11 or 12 PM through TH-cam, and the video makes my eyes bleed. Kind of hard to watch as you said. Cheers