@@ZoaibKhan Haha, yeah I lied. Never called her 😉 Anyway, if you are looking for video ideas... I found myself implementing stuff/components a second time, not remembering that I had implemented the exact same thing 1-2 years ago. That happened multiple times. So, having some nice searchable documentation about my (nx) repo would be really nice. That would help preventing re-implementing stuff. So, maybe you could do a video about documentation?
Worth to watch! Would like to improvise same app with sorting and checkbox functionalities in same manner as you suggested for better understanding and practice. Tons of thanks for the great & quality content. 😊
Thank you for a very informative video! I just have one question, is it better to have a second readonly signal in the service which has the value of the original signal? so that you are not directly bound to the writable signal? so that the last component always gets the value of the readonly signal and cannot change it many thanks !
Yes, that's a good practice to follow esp when working with large teams, so developers don't even mistakenly update service signals directly. Thanks for the comment! 🙂
Yeah, content projection is a special way to change a part of the component's contents. But not sure if it fits in with communicating with a component like an input does.
i am impressed, very sophisticated. Thank you for uploading.
Glad you liked it :)
very professional
Glad that you found it so! 🙏
Impressive technique shared in one video. Congrats, I'm really grateful!!
Glad it was helpful, Francis! :)
I gave Catie Nettleship a call and she approves this. Well done Zoaib!
Who's she? 🤔
Oh, I got it 😂😂 Thanks for the comment 😊
@@ZoaibKhan Haha, yeah I lied. Never called her 😉
Anyway, if you are looking for video ideas... I found myself implementing stuff/components a second time, not remembering that I had implemented the exact same thing 1-2 years ago. That happened multiple times. So, having some nice searchable documentation about my (nx) repo would be really nice. That would help preventing re-implementing stuff. So, maybe you could do a video about documentation?
Hmm, interesting. You're referring to documentation generators?
@@ZoaibKhan for example, yes
Worth to watch! Would like to improvise same app with sorting and checkbox functionalities in same manner as you suggested for better understanding and practice. Tons of thanks for the great & quality content. 😊
You're welcome 🤗 That can be a great followup video, thanks for the suggestion :)
Thank you
You're welcome 🤗
Nicely presented. Thanks!
You're welcome, Steve!
Thanks 🙏🏼
Welcome 🤗
Thank you for a very informative video!
I just have one question, is it better to have a second readonly signal in the service which has the value of the original signal? so that you are not directly bound to the writable signal?
so that the last component always gets the value of the readonly signal and cannot change it
many thanks !
Yes, that's a good practice to follow esp when working with large teams, so developers don't even mistakenly update service signals directly. Thanks for the comment! 🙂
Can you show content projection as well in this context
Yeah, content projection is a special way to change a part of the component's contents. But not sure if it fits in with communicating with a component like an input does.