How Did I Not Know This TypeScript Trick Earlier??! 

Thanks

Interesting. Thanks for sharing man!

Small tip, the type string | number | symbol is equal to the global type PropertyKey :) type Foo = PropertyKey; // ^? string | number | symbol

Why doesn't it create a table in my local db it pushes and migrate but does not create a table why tried many solutions not working

Great trick, I used to get the same result with function overloading but that require a lot of type checking.

I thought this was a parody account at first

Thank you for the terminology, I feel missing that makes it impossible to learn and compare techniques, so it is very much appreciated.

so what is type guards then?

@@gubatenkov Type guard is when you test a variable on which type it is in an if statement to narrow it down. You can use e. g. instanceof, typeof or the in keyword for this. There is a great logrocket post about this, if you want to know more! just Google type guard typescript and you will find it

@@gubatenkov Type guards are: const isString = (val: unknown): val is string => { return typeof val === 'string'; } You use the 'is' syntax to annotate a function to be a 'type guard', or 'type predicate'.

well said 👍

I learned this from elm

oh, that looks so much better

composition vs inhertitance?

@@lasindunuwanga5292 there is no inheritance because it is an interface. interfaces cant inherit as they dont have behavior

@@bernardcrnkovic3769 so you are telling me it is okay to build an heirachy of interfaces?

There is no need for using interfaces. Interfaces are much more extensive in terms of functionality than regular type aliases. Using the extends keyword is not more "explicit". Intersection types (with the & operator) have pretty much the same semantics. Interfaces should be used when describing abstract types (for example, when doing polymorphism). You should not use an interface if you're not planning on using the implements keyword on other concrete types. Interfaces are not as flexible as type aliases, because they only allow object types. Also, interfaces can be overwritten in other places of the code, just by having another definition of it, or even multiple other definitions. Type aliases are much more simple and generic, they are just a way to give some type a name in order to re-use it or export it. I would prefer something like that: type Person = { name: string } type Male = Person & { gender: 'male' salary: number } type Female = Person & { gender: 'male' weight: number } type Props = Male | Female

Yes, those are discriminated unions

I'm surprised so many people are finding out about this so late

Males are required to declare their salary, while females are required to declare their weight? Indeed, a very discriminatory union 😂

@@markzuckerbread1865 i feel like disciminated unions are 90% of what makes typescript awesome, everyone should know it

It's so weird that the newer typescript docs removed the docs for discriminated unions. You can only find it in the old docs

Same, really glad it's this easy

Cheers man

Mhmm that's interesting too. Thanks for sharing man, cheers

Can you kindly provide the link to this video?

@@Osirisdigitalagency Sure! ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-8HoOxOd86M4.html

I heard about that too! Very cool concept

You're welcome dude yeah I was really happy when I discovered this too

Thank you mean. That means a lot.

You could still make them optional! There really are some great benefits to this

awesome dude

What do you mean? Do you have a small example of it?

Unless he's using a plugin that manages imports behind the scene, I'd say this is because of a bug in VS Code that suppresses import errors when the target isn't exported. TypeScript won't compile it in this case, though.

yeah NO idea why this is, my vscode just started doing it. based

Because both child and parent are not modules, so Typescript treat them both as globals

Cheers man

Do you spread the rest of the props? Or do you destructure each prop of the native element?

hey that sounds interesting, could you explain it a little bit more? :) that sounds interesting but I can't really figure out what exactly to do with the "satisfies" keyword here

​@@ExtraterrestrialCatgirl yeah, maybe a code snippet would do

the satisfies keyword is super interesting too. Gonna look more into this typescript stuff, it's actually cooler than I thought

@Joshtriedcoding1 love the realization 5 hours later 😂😂

youre welcome dude

this is in the documentation?¡ :o

Youre welcome!

You're welcome dude, nice to hear

Gonna look into it, thanks for the suggestion dude

That's not exclusive to TypeScript. JavaScript has it, too

@@DubiousNachos huh yeah TIL. It does really help specifically in TS cos of what I said above. That is you can't even do something like 'if (person.salary === undefined)...' in the above case but you can use the 'in' keyword

Care to share?

Something like { a: number; b?: never; } | { a?: never; b: string; } ?

@@Ultrajuiced I've tried responding but my youtube comments are always deleted. oh well

You're welcome champ

nice!