React Components with GENERICS? - Advanced TypeScript

No video

React Components with GENERICS? - Advanced TypeScript

Рет қаралды 27,621

Күн бұрын

Become a TypeScript Wizard with Matt's upcoming TypeScript Course:
www.mattpocock...
Follow Matt on Twitter
/ mattpocockuk

Пікірлер: 21

@nick97000 2 жыл бұрын

Also found that adding a comma after the generic arg allows you to still use arrow functions

@PrevalentAA 2 жыл бұрын

Thanks!

@thgosii Жыл бұрын

nice

@alexandercherniavenko7363 2 жыл бұрын

You can use generic with an arrow function in jsx. To do so use next: (with comma at the end)

@ilonachan Жыл бұрын

because that way the typescript parser can tell the difference between a JSX tag and a generics list, right?

@PrevalentAA 2 жыл бұрын

Thank you Matt. These bite sized videos on more specific and localised topics are great. Keep them coming!

@workflowinmind Жыл бұрын

Very nice. This is now accepted too btw (0:37)

@mariolazzari Жыл бұрын

Brillant! Really helpful for typing mu custom data table component. Great job!

@williamcory4689 Жыл бұрын

You can also just use () => to make it not ambigious in tsx files

@amirbagjani5800 2 жыл бұрын

Thanks for sharing your knowledge 👍🏾 You can use this

@farahrayis5928 2 жыл бұрын

It's pretty cool indeed. Thanks.

@user-lm5ju8nc2t 2 жыл бұрын

I find your videos very cool! But it would be even cooler if you took a small js lib and taught generics by adding types to it, on real word example)

@neuodev Жыл бұрын

You are amazing!

@sergeymild 2 жыл бұрын

how will it looks like if i need wrap my component in forwardRef?

@NareshKumarPanneerSelvam 4 ай бұрын

how can we use generics for forwardRef type

@mattpocockuk 4 ай бұрын

www.totaltypescript.com/forwardref-with-generic-components

@archmad 2 жыл бұрын

You dont need to turn it into function, const is fine but use extends instead

@jeffnikelson5824 2 жыл бұрын

but be carefull since it's easy to lose type-safety with this approach

@mattpocockuk 2 жыл бұрын

Could you clarify what you mean?

@jeffnikelson5824 2 жыл бұрын

@@mattpocockuk I mean that the more complex you go on a generic component the more you get into trouble and find yourself writing high complexity logic and edge-cases that only apply to one specific type that you have to cover since its generic. Its fine for simple components but in a more advanced case it is better to write more code but therefore be rewarded with clear type-safety.

@mattpocockuk 2 жыл бұрын

@@jeffnikelson5824 It depends, you can constrain the generic that gets passed in so the part about 'high complexity logic' doesn't ring true for me if you have good constraints.