React Design Pattern : Container Presentational Pattern in React.js

[@SalimAbuubakarAhmed]

Welcome back Sir , Amazing Tutorial with clear Explanation Sir Thanks So Much

[@DipeshMalvia]

Thanks and welcome

[@shubhamgupta-bl1tr]

Nice please come up with more react design patterns

[@DipeshMalvia]

Thanks and sure

[@SalimAbuubakarAhmed]

Sir please I requested to make Node js express mong db more projects to learn more and more Sir I will wait it and I appreciate your Time and Effort Sir

[@DipeshMalvia]

I will try my best

[@ajiteshmishra0005]

While making final component to render
We write the code like
export default function App(){
return ()
}
OR
export function App(){
return ()
}
OR
function App(){
return ()
}
export default App;
OR
const App = ()=>
{
return ()
}
export default App;
What is the difference in these 4 types of "export" in React-JS??

[@TheGabrielMoon]

beginners DO NOT do this in a serious project. We have hooks now, they are enough to separated logic from UI. This pattern is very outdated and makes your project more complex to maintain.
You can also use typescript instead proptypes

[@somnathroy102]

Now this comment has put me in jeopardy whether to watch or not

[@DipeshMalvia]

Yes, I have mentioned the same if you we are using typescript you don't need proptypes for validation of props. However this pattern is still followed in large applications. Hooks is also one of the pattern but that doesn't mean this is outdated.

[@cyberpaimpol]

In this case contexts are the solution no ? Why a Component ?

[@DipeshMalvia]

If you mean Context API then it is used for the sharing data and creating global data store to share among not so complex applications. This is a pattern that helps you to achieve SOC.

[@cyberpaimpol]

@@DipeshMalvia Of course !

[@ridho.p2383]

2024 still use proptypes?

[@DipeshMalvia]

Yes, there are companies and applications I have seen where propstypes are used because they are not using TS.