Guess what, I stumbled upon this same article, I was too lazy to read it so I searched HOC on youtube and now this guy is just helping me read it. what could be more easy than this 😆
Since i discovered your channel i add your name to every youtube search i do,you are simply the best react tutor on youtube, keep up these videos! A video idea that i would love to see frrom you is " Migrating to typescript in react" where you explain why we use react with ts and all that related stuff.
Ohh, so those {connect, mapStateToProps etc} from 'react-redux' are actually HOC for class component because hooks can be only technically used in functional components! Damn! In one of the interviews I couldn't explain why we expliclty need these since we can do that same thing with Hooks for some conditional rendering to wrap child component for that matter. Now i understand, so thanks
Another pro for HOC is that you separate the concern of receiving data from rendering that data which makes the component easier to write and test. I still would prefer hooks in almost all cases but I think this point should have been mentioned in the article.
Guess what, I stumbled upon this same article, I was too lazy to read it so I searched HOC on youtube and now this guy is just helping me read it. what could be more easy than this 😆
This was just a reading. It would be interesting to have an explanation with more modern examples. Because this form is now considered a legacy.
What is the new way?
Hooks
A very good and informative content in a row
Since i discovered your channel i add your name to every youtube search i do,you are simply the best react tutor on youtube, keep up these videos!
A video idea that i would love to see frrom you is " Migrating to typescript in react" where you explain why we use react with ts and all that related stuff.
I have a JSX to TSX video actually! But will do more
thanks mate for great video :)
Ohh, so those {connect, mapStateToProps etc} from 'react-redux' are actually HOC for class component because hooks can be only technically used in functional components!
Damn! In one of the interviews I couldn't explain why we expliclty need these since we can do that same thing with Hooks for some conditional rendering to wrap child component for that matter.
Now i understand, so thanks
Reading this code without TS types is a torture....
Another pro for HOC is that you separate the concern of receiving data from rendering that data which makes the component easier to write and test. I still would prefer hooks in almost all cases but I think this point should have been mentioned in the article.
I want to test react app but i have "react router dom 6" i don't know how to test two libraries. I only starting to create tests
seldom use this pattern
after long time live web tab redux store are getting empty why?
nice video
Hi, thanks for your video. I want to ask, is your project React course covered about middleware?
Middleware isn't covered because we don't have a real backend! All of the data is mocked to make it easier for beginners to focus on the React part
Please do a video on Render prop pattern
Bro literally reads an article on the video
How high are you bro? 😁
Yeah pretty lame
"Button" component needs to receive and use "style" prop
Can you post a video about cross browser compatibility.
Can you do a review of my react project bro? I just want to know what things I am lacking to level up.
Hi
Render prop pattern
Aw, why you read article as always hehe
Diversifying my content a bit 😁
Good chanell, but BAD video. You’re just reading. I think it would be better if you wrote the code with TS in IDE
is this another word of Currying?