I did not ever search about this topic before, but today, I was thinking of converting to tsx, and when I opened youtube, I found it on the top without searching😂
One of the most interesting topics i waited for, i really wanted to know what are the main section of a jsx file that is good if to be written with types and what are less important as typescript will auto deduce it. Thanks and keep going 💕.
5:50 I think, it's not a good idea to explicitly write the return-type of fetch() without proper json-schema validation. Inferring types from something like Zod after validating will ensure better type-safety.
This might be unpopular opinion and personal preference. I understand the purpose of Typescript was created. But I also understand purpose of Javascript was invented. Javascript created to help human to programming easily. Easy to read, universal, simplicity, and versatile. Because we are not a computer. So, it's not human level to make a type checking, make it looks complicated. When we put a variable, we are as a human already know which one a string, number, or boolean without unnecessary things to describe. Let computer does (low levels). It's not Javascript does. And it doesn't mean Typescript comes in to solve those issues. When other thing comes to simplifies an issue (ex: Redux to React-Query), Typescript was the opposite. Typescript just makes programming more complicated. Also makes the syntax looks ugly.
"Javascript created to help human to programming easily" something simple. Good luck to maintain a project with hundreds of different types without types. "When we put a variable, we are as a human already know which one a string, number, or boolean without unnecessary things to describe. " But sometimes you open 20 different files, trying to figure out what properties/types do you have in this complex object with 200 properties instead of simple mouse hover with TS.
I did not ever search about this topic before, but today, I was thinking of converting to tsx, and when I opened youtube, I found it on the top without searching😂
real wai
You are the best react instructor sir!
You always ships the quality to us.
Love from Budapest
It was a great video especially for people like me who are junior devs planning to start learning typescript. Thank you!
Oh my gosh this is so good I need more episodes please make them.
It's kind of beginner+ tutorial, but can save like an hour or so. Well made, thanks!
Nice explanation and straight to the point.
I suggest some videos about handling different kinds of errors in react and ts
Great tutorial! Need second episode! Maybe the topics can be: passing the props/states to another component, etc
woah we really need this kind of rare content
Converting JSX to TSX in React, so clearly explained. Thank you, Darius
{2024-06-21}
Thank you so much. Very helpful for me right now because I'm converting my e-commerce project react app into typescript.
This was great, I hope you can a part 2 where you go into more details about using typescript with react
Your Quality of presentation increasing day by day.
Thank you for saying that! I'm really working on it ☺️
please make full tutorial on Zod. And other similar libraries too
One of the most interesting topics i waited for, i really wanted to know what are the main section of a jsx file that is good if to be written with types and what are less important as typescript will auto deduce it.
Thanks and keep going 💕.
out of sudden i realise you look alike Mauricio Pochetino 😅
can you have a video about typescript. thanks
Is it normal to define types in the same file? Or do people define all the types separate files and import the props?
Great video!
Most types are defined in the same file! Only types of shared things are outside
#IdeasForContent. Can You make tutorials on the following topics please) : GraphQL, Socket io
5:50 I think, it's not a good idea to explicitly write the return-type of fetch() without proper json-schema validation. Inferring types from something like Zod after validating will ensure better type-safety.
What is the difference between interface Props and type props??
Not much, both can be used!
@@cosdensolutions ahh I see thanks for response ❤️
this is what i need
Hello thanx for video first , Second i want to ask you if i learn nodejs in 2024 so i can fined a job with it ?
❤❤❤
🌅
You are great ❤❤❤❤
Egyptians loves you ❤❤❤❤
This might be unpopular opinion and personal preference.
I understand the purpose of Typescript was created. But I also understand purpose of Javascript was invented.
Javascript created to help human to programming easily. Easy to read, universal, simplicity, and versatile.
Because we are not a computer. So, it's not human level to make a type checking, make it looks complicated. When we put a variable, we are as a human already know which one a string, number, or boolean without unnecessary things to describe.
Let computer does (low levels). It's not Javascript does. And it doesn't mean Typescript comes in to solve those issues.
When other thing comes to simplifies an issue (ex: Redux to React-Query), Typescript was the opposite.
Typescript just makes programming more complicated. Also makes the syntax looks ugly.
"Javascript created to help human to programming easily" something simple. Good luck to maintain a project with hundreds of different types without types.
"When we put a variable, we are as a human already know which one a string, number, or boolean without unnecessary things to describe. " But sometimes you open 20 different files, trying to figure out what properties/types do you have in this complex object with 200 properties instead of simple mouse hover with TS.
Thank you for a great summary - it's a skill set I need to finally love and embrace. Tried to get around it but it's not working .