How I Write Clean Code in React

Рет қаралды 32,391

Cosden Solutions

Күн бұрын

Пікірлер: 74

@johndevnoza4223 6 ай бұрын

as a begginer one, im doing this by habbit and i was scared if it was overkill or not. now i feel happy!

@fanespratama 6 ай бұрын

Take a note that when you use the custom hook with useEffect in more than one file, the useEffect will run more than once, so keep one custom hook for every layout/component (let say one for user list, one for user details). If not, just move the useEffect outside the custom hook

@dr_jacko 6 ай бұрын

This is a good start, but in general I would prefer to abstract fetch away a step further than hooks or components and you also need to handle loading and error states with your async calls. As an example, create a UserProfileRepository and UserProfileService classes which have functions for CRUD on UserProfiles. Use the singleton pattern on these classes and keep them in a context where it is required in the app.

@vladanisov1689 6 ай бұрын

definitely the best approach for this kind of scenario!

@shoaib_akhtar_1729 4 ай бұрын

Thanks for explaining the importance of achieving modularity in our code.

@sachityadav4141 6 ай бұрын

This was Needed 😀 ThankYou, i was having anxiety seeing lots of styling classes in return of every component

@devquen37 5 ай бұрын

PageLayout -> ProfilePage -> ProfileData -> Children Components (Avatar, PostList, etc)

@moonshadowwlb Күн бұрын

Thanks, ill try this in old prijects to see if i can improvement

@hooooman. 6 ай бұрын

A beginner here, this approach definitely makes our code more clean. but my doubt is, say if we are building a little advanced/complex project, the same approach makes too many folders and files ?

@calmmind3160 3 ай бұрын

mate, i'm enjoying your react content, this is what i need to learn, keep making content

@roshanmaddumage9675 3 ай бұрын

I'm truly captivated by your content and watch it daily during my free time. Please continue to create great content. Regarding this video lesson, I have a question: How do you plan to organize the subcomponent or child component files when you break down a large page into smaller components?

@cosdensolutions 3 ай бұрын

Thank you for the kind words! You follow the single responsibility principle. Each component only does one thing until you've run out of things to do. So page component renders page and all features on page, then each feature gets its own component for the feature, and each one of those uses other components that make up the feature. There isn't really a strict rule as to how exactly, but rather it all depends on the features themselves and how logical it is to separate them. But generally following the SRP is a great way

@roshanmaddumage9675 3 ай бұрын

@@cosdensolutions Great! I had a small doubt and now it's cleared. Thank you for the reply. ☺

@2positive1 5 ай бұрын

I would move static data array upper, from the App component. It’s static, no need to recreate it on every re-render.

@QueeeeenZ 6 ай бұрын

I think you can use Nuxt and all the layout, structure will be already configured for you out of the box.

@mulengachitalima7695 6 ай бұрын

Awesome video.. Really appreciate how you always adhere to SOLID principles in your videos

@viophile 6 ай бұрын

What is your view on default exports? In my opinion they should only be used in libraries, not in any other code.

@mahendrasinh_9106 6 ай бұрын

if you export as a default then you can import it at any name // Exporting a component with export default const MyComponent = () => { // Component implementation }; export default MyComponent; import MyComponent from './MyComponent'; without export default // Exporting a component with named export export const MyComponent = () => { // Component implementation }; // Importing the component import { MyComponent } from './MyComponent'; you need to call with same name

@PaulSebastianM 6 ай бұрын

Default exports should be banned. They are not adhesive to strong typing and make tree shaking impossible especially when mixed with named export.

@sontranvan5348 6 ай бұрын

Simple, effective tips that are easy to learn and apply. Thank you for sharing your knowledge!!!!

@SahilPatel-kh2rt 6 ай бұрын

Hey, which vs code theme you are using.? Excited to use it for my self also.

@mashab9129 6 ай бұрын

why not having ProfileData component call the useFetchProfile ?

@skymasseffect 2 ай бұрын

can you make a video on MVVM architecture with react ?

@ianfrye8988 6 ай бұрын

Great video. Only question I have: why not move the useFetchProfile inside the ProfileData page instead of passing it as a prop?

@ExileEditing 6 ай бұрын

I struggle with choosing between fetching on the page and passing down or fetching in the components as well. I think it makes sense for both, but it is better if you separate concerns and fetch from the page. This way, your component only cares about rendering and doesn't deal with how it gets the data. It makes those components simpler as well and probably easier to test

@cosdensolutions 6 ай бұрын

because ProfileData is only responsible for rendering, not fetching. Also, if you want to show profileData but with different filters or page sizes, adding that inside will be a mess. The way I did it, the parent decides that and just gives it to ProfileData to take over. It's simpler

@ianfrye8988 6 ай бұрын

@@cosdensolutions Thanks for clarifying!

@sontranvan5348 6 ай бұрын

@@cosdensolutions but in case I need to use the data of filters or page sizes from ProfileData to refresh profiledata, should I use a callback to left it to ProfilePage or move fetching into ProfileData component?

@kalideb-y3y 6 ай бұрын

should I still separate the fetching hook if only one component uses it?

@meylis_so2 4 ай бұрын

cosden how are u making sidebar in vscode and how u are controlling it please make tutorial

@cosdensolutions 4 ай бұрын

telekinesis

@harithsenevi4 6 ай бұрын

Can't we just use the useFetchProfile hook inside the ProfileData component itself instead of passing profileData as props from ProfilePage component? Is it a bad practice? What complications could have with that approach?

@bruce_k3lly 6 ай бұрын

Thank you for this amazing video it's really helpful and it has increased my productivity, but can I use utils folder, as you said and just add reusable function for similar work ?

@carloseduardomagalhaespere5112 6 ай бұрын

Thank you for another great video! I've been learning a lot here! One question: Why do you prefer to use type instead of interface in the props definition? 🤔

@kit3x663 6 ай бұрын

I have one question. Why you didn't use React.FC or forwardRef in any of your videos. Is it usseles to use?

@JericAdriano-yo9pv 6 ай бұрын

How about modals or dialogs that are used in one page? Do we handle them all in the parent component?

@lyrical6852 6 ай бұрын

Honest question, are you doing this in the real world app or in your work?

@Makłowiczwpodróży-q6l 6 ай бұрын

Perfect timing, just wanted to learn about those :D

@gherardivictor 6 ай бұрын

Good quality and valuable content, thanks

@edward-vonschondorf-dev 6 ай бұрын

Great video Cosden! It's definitely something I've been looking into lately cause I don't like long complex components that I have to edit/create. I was just curious about something though, i noticed in your imports you have an @ symbol at the beginning and was wondering how that was setup and if there is an advantage to it? Thanks!

@cosdensolutions 6 ай бұрын

it's import aliases, the advantage is it makes things cleaner, and if you move things you don't have to always have everything be rewritten

@isaacjames8735 6 ай бұрын

Make a video about Social Login system in react please

@techaddictdude 6 ай бұрын

Shouldn't the PageLayout.tsx be located in the pages folder, while the 'Profile' file should be in the in components?

@tunde6159 6 ай бұрын

Such good tutorials.

@64revolt 6 ай бұрын

What do you think of atomic design and styled components? Only got to the page layout so far, but that seems like a perfect case for that, no?

@MohamedRabi 6 ай бұрын

Thank you for the fantastic content!

@FiguringOutWhatIsLife 6 ай бұрын

I mean isn't the children example you gave in the first one just what we do in App.jsx though?

@delightful209 6 ай бұрын

is it me or is the audio levels on this video really low. i have my headphones at 50 % and its quite low compared to other videos

@FalioV 6 ай бұрын

Why would you use this Layout component on every page like this ? Just pass it to the index route and thats it. Overall I see this is "basic 101" and way far from Sr. react code. And I personally think this is not the best way to describe "custom hooks" as it should be. This profile code belongs to the Service layer. Don't get me wrong, I'm not here to argue, just have some questions over all. :)

@RoomCorner_ 6 ай бұрын

Sir i'm interest of React Project but my english isn't very well. Is there subtitle like in KZbin?

@cosdensolutions 6 ай бұрын

yes there is!

@SingleSeeker 6 ай бұрын

in a real project , a loading , error is also needed.

@programmerjowo 6 ай бұрын

How to handle authentication on the API

@sathirabandara7981 6 ай бұрын

great video. its very useful. 🤩

@shakapaker 6 ай бұрын

props with children makes children optional, for layout it needs to be required

@Divyv520 6 ай бұрын

Hey Man , really nice video ! I was wondering if I could help you with Viral Content ideas in your niche , Script , editing , thumbnail , SEO , Growth and analysis , Leads and appointments for your business , etc in all to you ! Pls let me know what do you think ?

@Edgars82 6 ай бұрын

export const router = createBrowserRouter([ { path: '/', element: ( ), errorElement: , children: [ { index: true, element: , }, { path: 'search', element: (... this way all childrens will have layout and no need to import it as wrapper inside page components