I like to think about generics as boxes. So a Box is an empty box that could hold anything. A Box is a box that contains only books. I like to use the analogy of moving. If you don't write what is in a box on the outside, it could hold anything, and you have to open it to know what room it is for. However, much like generics, if you write what the box contains on the outside, you can move it to the appropriate room and be confident in what it contains. Generics are the same idea. You tell the code what this generic contains, and it doesn't need to unpack everything to use it. In fact, unpacking a collection that isn't generic is called "unboxing."

@@xocomil A very good analogy, Jason!

Thank you

Nice! Just wanted to point out that if your component (and template) aren't generics, then it is significantly simpler to add type-safety 😋

@@ChauTran yea definitely. should be stated that this approach is great for dumb components that can expect any Input data shape. so if the Input is type "any", this is a great way to type it. is this what you mean?

Anything specific you'd like to see?

@@JoshuaMorony Any widgets or cdk that you can think of, that we are regularly using in our projects. Like side bar, navbar (nested), linked with the router. If we changed the route from the window search url that activated route of the sidebar will be automatically showing activated. One more thing is using generics how we can get more advantages in angular. I know in react there are multiple use cases with typescript like polymorphic component and custom hooks. I want to know how angular uses generics in material component or other libraries ant design component. One scenario like if how we can strongly typed the component that are passing through ng-content. Content projection is one of the key feature for reusability right. Thank you so much for sharing. 🙏👌🤘

I rechecked and I was wrong about this, apologies for just anyone stumble upon this. 😅

I don't know if I'm cut out for live streams, I can't even deal with my wife looking over my shoulder when I code!

@@JoshuaMorony haha, if u ever do do it tho i have a feelin ppl would like it. and that way youd be able to teach your wife to code too haha! but either way i appreciate the vids brother

Are you building a form builder. I guess you would need a factory component that can create other components based on input resource type it should process. Then you'll need a good or okay enough generic interface to express your source input(data type, name, validations, optionals and miscellaneous data) that be based to your factory component. Take a look at react mui or ng zoro

Yes. If you expose that method on the TemplateRefContext

ng-content won't work because you cannot pass context back to ng-content. In the example, Table component is what iterates through the Array of items then we allow customization via TemplateRef; we can then pass each item in ngFor back to the TemplateRef if it's provided. ng-content won't have this