How I Write Clean Code in React
Vložit
- čas přidán 27. 07. 2024
- Check Out Brilliant → brilliant.org/CosdenSolutions
🚀 Project React → cosden.solutions/project-react
Join The Discord! → discord.cosden.solutions
VSCode Theme | Font → Material Theme Darker | Menlo, Monaco "monospace"
In this video I will show you how I write clean code in React. I will show you my mindset, how I approach a problem, and how I break it down into multiple small parts to make it manageable and scalable. Through this video you will learn how to write better React code yourself, and become a better React developer!
Thanks for explaining the importance of achieving modularity in our code.
as a begginer one, im doing this by habbit and i was scared if it was overkill or not. now i feel happy!
Awesome video.. Really appreciate how you always adhere to SOLID principles in your videos
This was Needed 😀 ThankYou, i was having anxiety seeing lots of styling classes in return of every component
Perfect timing, just wanted to learn about those :D
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.
definitely the best approach for this kind of scenario!
Good quality and valuable content, thanks
Simple, effective tips that are easy to learn and apply. Thank you for sharing your knowledge!!!!
Thank you for the fantastic content!
great video. its very useful. 🤩
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!
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
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? 🤔
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 ?
Such good tutorials.
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 ?
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
PageLayout -> ProfilePage -> ProfileData -> Children Components (Avatar, PostList, etc)
Hey, which vs code theme you are using.? Excited to use it for my self also.
How about modals or dialogs that are used in one page? Do we handle them all in the parent component?
should I still separate the fetching hook if only one component uses it?
Shouldn't the PageLayout.tsx be located in the pages folder, while the 'Profile' file should be in the in components?
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?
I have one question. Why you didn't use React.FC or forwardRef in any of your videos. Is it usseles to use?
why not having ProfileData component call the useFetchProfile ?
I would move static data array upper, from the App component. It’s static, no need to recreate it on every re-render.
I mean isn't the children example you gave in the first one just what we do in App.jsx though?
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?
Great video. Only question I have: why not move the useFetchProfile inside the ProfileData page instead of passing it as a prop?
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
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
@@cosdensolutions Thanks for clarifying!
@@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?
Honest question, are you doing this in the real world app or in your work?
I think you can use Nuxt and all the layout, structure will be already configured for you out of the box.
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
What is your view on default exports? In my opinion they should only be used in libraries, not in any other code.
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
Default exports should be banned. They are not adhesive to strong typing and make tree shaking impossible especially when mixed with named export.
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 ?
Make a video about Social Login system in react please
cosden how are u making sidebar in vscode and how u are controlling it please make tutorial
telekinesis
anyone know what allows him to do rjsfc and have the react component with function keyword? i just have rafc and its the arrow funciton i hate it
check out my vscode setup video
why would you use export default function instead of export const?
@@nicus1504 i just like using function better its personal preference
How to handle authentication on the API
Sir i'm interest of React Project but my english isn't very well. Is there subtitle like in CZcams?
yes there is!
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. :)
in a real project , a loading , error is also needed.
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
in your video description ,the project react lik is give me 500 web code .
props with children makes children optional, for layout it needs to be required
يمزاجك يا كوزدين
Lol react andies
Increase your voice please... Its so low.... Thanks for zooming screen
nah I like it because he’s not yelling or doing a “youtuber voice”
I’m not just being contrarian. His level are fine.
His volume level is good,try to check your speaker
If only there was a way to increase the volume of a video??!?
throw your speakers in the trash and get new ones.