To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/PedroTech . You’ll also get 20% off an annual premium subscription.
Bro please start the backend series with node js beginners to advanced all things please i learn front-end from you Edit : hey Pedro by see likes you know what people want
Thanks Pedro! I was hoping if you can jump into some Design Patterns we can use in React? (eg: Provider Pattern, 2. Hooks Pattern, 3. Presentational & Container Component Patterns, 4. Render Prop Pattern, 5. High Order Component (HOC) Pattern.)
separate the container and the presentational component for testing purpose use redux for the state management for data fetching make use of react query clean up the effect when unmounting
I like atomic design for components, with atoms, molecule, organisms & page at least, to organise file structure Then we add folders : Utils/ Context/ Hooks/ Routes/ Services/
From my experience I’d like to share some info. The RxJs together with Graphql and TS works very well. It allows you to create flexible states and in additional you will be able to create a service layer that will be responsible for managing your requests (queries,mutations). Pedro, have you ever used such things?
About single responsibility component or independent component. I'm currently learning about redux and testing, and when i test a component that use useSelector in it, it became too complicated that i gave up. So i change that component to use props. I'm confuse about the single responsibility or independent component. is a component that use useSelector an independent component or a component that use props that an independent component??
I use ABC structure. Which is something I came up with to simplify the way I manage react apps. a - app (To manage navigations and routing only) b- boards ( Are smart components take care of fetching and logic ) c - Components ( UI components that only receive props and can handle empty props ) --- This was my best solutions honestly it helped alot to have a clean app structure where I can immediately know the hierarchy of a certain element in my app. Also, I no longer use /src folder. Finally I changed (assets) folder to (resources) and (context) folder to (stores).. and so many other things to keep my app folder strcture clean without having to many folders start with the letter "c" for example (components, constants, context ..) so for constant I gave it a folder named "keys" this way the folder structure becomes a very nice top to bottom structure with the most important element is on top "app" and the least important elements are at the bottom "widgets, and zod" for mini components and validations that you only touch once and can copy and paste between projects without changing anything.
To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/PedroTech . You’ll also get 20% off an annual premium subscription.
Bro please start the backend series with node js beginners to advanced all things please i learn front-end from you
Edit : hey Pedro by see likes you know what people want
Honestly we need it also.
bro wasted one third of his video on intro and ad
starts at 2:58 btw
2:58
pedro pedro pedro pedro pe 🕺🕺🕺🕺🕺
Thanks Pedro! I was hoping if you can jump into some Design Patterns we can use in React? (eg: Provider Pattern, 2. Hooks Pattern, 3. Presentational & Container Component Patterns, 4. Render Prop Pattern, 5. High Order Component (HOC) Pattern.)
Nah this was a lazy video. Sorry not this one bro. Kinda just a lazy put together and voice over to make some money.
Thank you Pedro 🤠
bros selling out
Damn im early af, 6 minutes
nice video Pedro , thx for your advice
Pedro is brabo. Thanks for the video, it helped me a lot!
Need a project which works on react hooks for optimization 💥
separate the container and the presentational component for testing purpose
use redux for the state management
for data fetching make use of react query
clean up the effect when unmounting
I like atomic design for components, with atoms, molecule, organisms & page at least, to organise file structure
Then we add folders :
Utils/
Context/
Hooks/
Routes/
Services/
From my experience I’d like to share some info.
The RxJs together with Graphql and TS works very well.
It allows you to create flexible states and in additional you will be able to create a service layer that will be responsible for managing your requests (queries,mutations).
Pedro, have you ever used such things?
Thanks pedro ,We all love you ,In future your talent will beat ,🧡🧡💥💥
TY Bro
About single responsibility component or independent component. I'm currently learning about redux and testing, and when i test a component that use useSelector in it, it became too complicated that i gave up. So i change that component to use props. I'm confuse about the single responsibility or independent component. is a component that use useSelector an independent component or a component that use props that an independent component??
I highly suggest to try using Feature-Sliced Design :)
We want backend from you in Node.Js and Next 😘😘😘
pls create a sinlge mysql video
Brazilian compliments to this great video!
Hey pedro learned a lot from you , love you bro.
lets get this guy to 200k subscribers
Much insightful video @pedro
Pedro are you from Brazil?
Please create mern project
Nice style man! Noooix Pedrão monstroo
Tq
I use ABC structure. Which is something I came up with to simplify the way I manage react apps.
a - app (To manage navigations and routing only)
b- boards ( Are smart components take care of fetching and logic )
c - Components ( UI components that only receive props and can handle empty props )
---
This was my best solutions honestly it helped alot to have a clean app structure where I can immediately know the hierarchy of a certain element in my app.
Also, I no longer use /src folder. Finally I changed (assets) folder to (resources) and (context) folder to (stores).. and so many other things to keep my app folder strcture clean without having to many folders start with the letter "c" for example (components, constants, context ..) so for constant I gave it a folder named "keys" this way the folder structure becomes a very nice top to bottom structure with the most important element is on top "app" and the least important elements are at the bottom "widgets, and zod" for mini components and validations that you only touch once and can copy and paste between projects without changing anything.
Boa Pedro! Brasil aqui
Thanks for the video Pedro
🎉