Turning bad React code into senior React code

Поділитися
Вставка
  • Опубліковано 3 сер 2023
  • Join The Discord! → discord.cosdensolutions.io
    Welcome to Code Review!
    This is a series of videos where I review code that you send me or that I find online. I review the code as I would when I work with my clients. You will see how a senior developer looks and thinks about code in a variety of scenarios, learn about best practices and how to do things the right way, and learn how to become a better developer overall.
    Enjoy!
    Darius

КОМЕНТАРІ • 138

  • @novailoveyou
    @novailoveyou 9 місяців тому +70

    The first example has more to learn! Take the routes variable outside of the App component and put it on the same scope as App. That way we're saving ourselves a bit of performance and improving reliability. Also const variables like routes we could name ROUTES in all caps to indicate that that's something constant and within our frontend App

  • @icoderdev
    @icoderdev 10 місяців тому +38

    Restructuring another Developer's code is one of the highest skill to possess. Thanks cosden solutions

    • @cosdensolutions
      @cosdensolutions  10 місяців тому +3

      You're most welcome ☺️

    • @kollpotato
      @kollpotato 10 місяців тому +7

      Not always, because it's much easier to see other people's mistakes than your own.

    • @owenwexler7214
      @owenwexler7214 9 місяців тому +7

      Refactoring your own code from more than 6 months ago is essentially the same thing.

  • @vojinmilovic5787
    @vojinmilovic5787 9 місяців тому +131

    I don’t think anyone mentioned that the access token was passed through url which is as insecure as it can be

    • @simonesquillace1624
      @simonesquillace1624 9 місяців тому +13

      Yea, he refactor bad react code… so yes looks good but the implementation still sucks. Honestly doesn’t look senior to me

    • @emanuellamba5828
      @emanuellamba5828 9 місяців тому +3

      I'm not a Web Dev but that was my first thought too

    • @weiss588
      @weiss588 9 місяців тому

      how should it be passed then?

    • @emanuellamba5828
      @emanuellamba5828 9 місяців тому

      @@weiss588 through POST calls to the server

    • @santiagobarrera2387
      @santiagobarrera2387 9 місяців тому

      @@weiss588An authorization header (bearer token) or cookies. And that can only be considered secure if the connection is made over HTTPS, otherwise there’s no (simple/elegant) secure way

  • @saqibmuhammad7218
    @saqibmuhammad7218 10 місяців тому +1

    One of your well wisher and Keep it Up you are doing amazing work. I learn a lot of things from your videos and shorts,❤

  • @2gbeh
    @2gbeh 10 місяців тому +58

    Perfect, but one more thing, your custom hook is supposed to accept the api endpoint as a parameter because its actually different in both places used from the original code. That is, "survey/link/pd-.." and "survey/link/energy-.."

    • @cosdensolutions
      @cosdensolutions  10 місяців тому +17

      Yes you're totally right! Realized this after I filmed the video 🥲

  • @hritikkumar2554
    @hritikkumar2554 9 місяців тому +5

    Sol 1: we can also fetch the path text when it gets clicked and we define the onClick method in context and then we can set the path by string concatenation.
    This will help us to get rid of the array that you just created.

  • @Shaheer-xs5os
    @Shaheer-xs5os 10 місяців тому +4

    Man you are one of the best teacher ever, I have watched your react-hook videos and they're so good, respect you 💕

  • @harag9
    @harag9 7 місяців тому +2

    Just found your channel, and watching some of your stuff (and subbed). the useEffect actually runs twice and you should code it as such, it runs twice in DEV mode, but when live it will run once. React 18 is when I believed this changed. Because you're calling an API in the useEffect, you will also need an Abortcontroller, and a cleanup in the useEffect to abort the first run. It's a good habit to get into. So far liking your channel.

    • @cosdensolutions
      @cosdensolutions  7 місяців тому +1

      yep, you are totally correct! glad you enjoy the videos!

  • @amey4521
    @amey4521 9 місяців тому +5

    A more efficient way of handling protected routes would be to create an protected route component to wrap unprotected routes.

    • @michaelczolko6093
      @michaelczolko6093 4 місяці тому

      100% agree, senior developers use composition instead of props in object array and later mapping with conditionals...

  • @dylanarmstrong9328
    @dylanarmstrong9328 8 місяців тому

    As someone who uses the nextjs framework watching you go through the route code was really funny to me. Great solutions though because of dry principle. 😁

  • @slavenDj
    @slavenDj 9 місяців тому +4

    Great video. I use shortcut F2 to rename variables, saves a lot of time, and it's safer.

  • @tunoajohnson256
    @tunoajohnson256 7 місяців тому

    Good stuff! Cheers for sharing

  • @Alxndr0
    @Alxndr0 9 місяців тому +2

    Nowadays everybody with good speech in a relaxed environment can be seniors 😂

  • @pyyrr
    @pyyrr 9 місяців тому

    code in the thumbnail is absolutely amazing

  • @sonhuynh570
    @sonhuynh570 10 місяців тому

    this process remind me the old time lmao btw great vid and keep it up bro

  • @sbabup8957
    @sbabup8957 8 місяців тому

    Never subscribed to anyone before, You are the first. Keep up the good work!! Also whats the font in your editor? I liked it alot..

    • @cosdensolutions
      @cosdensolutions  8 місяців тому

      damn, that means a lot! I use the menlo, monaco font. My next video is actually all about my custom vscode setup!

  • @user-nl2ct8jn9k
    @user-nl2ct8jn9k 7 місяців тому

    Nice and informative video. Do you by chance have any video about organising files according to features and not types in nextjs?

    • @cosdensolutions
      @cosdensolutions  7 місяців тому

      I have a video on general folder structures in React, but nothing that specific unfortunately

  • @Gilderbrant
    @Gilderbrant 9 місяців тому +26

    7:25 I think this pattern is used to prevent double call of useEffect in the strict mode (react 18).

    • @cosdensolutions
      @cosdensolutions  9 місяців тому +9

      could be yes, but that's totally the wrong way to approach it

    • @muratcemyalin
      @muratcemyalin 9 місяців тому +8

      you just could have memoize the function with usecallback and give it to useeffect dependency array

    • @Isaac-hd6vs
      @Isaac-hd6vs 9 місяців тому +10

      @@cosdensolutionsyou sure? That’s how the new react doc suggests clean-ups do be done

    • @rosssharma542
      @rosssharma542 9 місяців тому +1

      @@cosdensolutions What's the right approach? This is the pattern suggested in the official React docs.

    • @inakiarias7465
      @inakiarias7465 9 місяців тому +2

      I think the point of Strict Mode running Effects twice is so that you can notice if your effects have unintended side effects if they run more than once. In this case it does, the fetch is running twice, so according to "good practices" you are making an error.
      The usual way to solve this "fetch inside useEffect" is to use the AbortController technique, where you pass a signal to the fetch call, and when you return from the effect, inside the cleanup function you abort with controller.abort.
      You can google it pretty easily, but basically each time the effect runs it will cancel the previous fetch, which should be "intended behaviour"

  • @nicolamigone8849
    @nicolamigone8849 9 місяців тому

    Are you going to do more of these? I'd love to have my code reviewed

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      Yes! Post it in the Discord there's a channel for that

  • @thecyberhobbit
    @thecyberhobbit 9 місяців тому

    "Route" !== "Root" 🤣😂
    Jokes aside, nice video dude, keep it goin!

  • @LePhenixGD
    @LePhenixGD 9 місяців тому +4

    6:20 I believe you should've used the .set() method of the .searchParams setter instead of directly assigning a new URLSearchParams object, if you wanted to assign the parameters your way you should use the .search setter instead

  • @rajendra222php
    @rajendra222php 4 місяці тому

    we need more video like this

  • @AnPham-uz3td
    @AnPham-uz3td 9 місяців тому +6

    At 1:50 I completely disagree with you, in a fast pace code changing webapp, I usually see people rewriting/enhancing the root routing of the app (like adding a new login OAuth handler, add logic to track user behavior on specific route of the app with utm, etc). Rewriting it to an array and .map does make the code smaller, yet it makes the code coupling (please google the term "coupling") into your own logic, hence it may gets in other developer's way if they want to add new feature, which is bad for new feature and bad for the business.
    Actually, the more time I live inside the coding world, the more I see that the best code is the most simple one !

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      Fair point, but this is a mature project and for its use cases this was an improvement. But it ultimately depends on the project. Not every project needs a complex routing structure

    • @Mr8000D
      @Mr8000D 9 місяців тому +1

      @@cosdensolutions Nearly every routing file looks like the one you showed. It's already easy to read, and add a route. If I open the routing file and it has a loop in it just to reduce the lines in the file, I am not seeing how this is improving readability.

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      @@Mr8000D it's making you not have to repeat all of the same components and auth router. If they're all the same, it's just easier to have a loop so you have one place to look at how everything is rendered

    • @m.syafaat
      @m.syafaat 9 місяців тому +6

      ​@@cosdensolutions You seem to be misunderstanding the concept of "repetition" or you might heard of the DRY (Don't Repeat Yourself) principle. In this case, converting your component into a map doesn't actually improve your code, it could make it worse. It appears that you're introducing a new approach to rendering your routes, which doesn't necessarily align with good coding practices. If this were in my team, I would likely express my confusion with a "WTF", and then suggest, "Please, consider creating a new Route Component named AuthRoute and use it like a standard Route: .".
      Every time I see people doing something like this, I'm 100% sure that it's a sign of a junior developer.

    • @filipecovas
      @filipecovas 9 місяців тому +1

      Completely agree, the map will increase the coupling and decrease de legibility and also some bad performance.

  • @osamaakhtar6525
    @osamaakhtar6525 9 місяців тому +2

    4:15 Interestingly enough you could have placed the routes object outside the App component since it didn’t depend on any reactive variable.

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      Yeah you could've, but that's just personal preference at that point! Wouldn't affect performance in any way

    • @muratcemyalin
      @muratcemyalin 9 місяців тому +2

      @@cosdensolutions i am using the same technic with just making a seperate routes.js file and exporting routes from there and importing to app just a little bit cleaner.

  • @piotrzajas9014
    @piotrzajas9014 9 місяців тому

    4:04 - You can prolly delete the at the end of map func and make the a self closing tag?

  • @jeanmax1me
    @jeanmax1me 9 місяців тому

    Very nice

  • @carlosmaralit8784
    @carlosmaralit8784 9 місяців тому

    this is so useful, can you also make like this with codeigniter? thanks

  • @devyb-cc
    @devyb-cc 8 місяців тому

    i believe react router has component called RouterProvider to handle the first use case.

  • @terjeoseberg990
    @terjeoseberg990 9 місяців тому +1

    At 6:55, all my useEffects run twice. I had to do something similar to prevent code that I want to run once from running twice. It seems to be some sort of development debug mode. I don’t like having this code, but I have it because I have no choice.
    Is there a better solution?

    • @cosdensolutions
      @cosdensolutions  9 місяців тому +1

      Everything runs twice in strict mode, that's on purpose. It's to prevent from making mistakes in your effects. The effect should have no problem running twice, if it does, you need to change it!

    • @terjeoseberg990
      @terjeoseberg990 9 місяців тому

      @@cosdensolutions, I don’t understand how running all the useEffects twice prevents people from making mistakes.

  • @imrahulkhatri
    @imrahulkhatri 8 місяців тому

    Very helpful

  • @zyph.
    @zyph. 2 місяці тому

    Nice video that shows your thought process. I don’t agree that turning the routes into an array is making the code simpler / more readable. It makes it less flexible. Imo a better solution would be to create e.g. a AppRoute component that hides a lot of the boilerplate for you. Feels more React-ty

  • @navidghasemi9685
    @navidghasemi9685 9 місяців тому

    great that was helpful

  • @dgoenka1
    @dgoenka1 9 місяців тому

    1:55 how about a custom component and pass it to that?

  • @hritikkumar2554
    @hritikkumar2554 9 місяців тому

    And yes, you are awesome 👍

  • @af2b
    @af2b 9 місяців тому

    Amazing

  • @p1erceprc
    @p1erceprc 8 місяців тому

    What theme is this? thanks

  • @user-eo3he8ig3b
    @user-eo3he8ig3b 9 місяців тому

    please make one javascript tutorial you are explaining fabulous

  • @aymenbachiri-yh2hd
    @aymenbachiri-yh2hd 29 днів тому

    Thank You

  • @groovebird812
    @groovebird812 9 місяців тому

    First you return generateURL, AuthToken and url and at the end end of the video only url? This was to quick for me

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      Yeah I thought initially we would need to return all 3, then we only needed the token so I changed it

  • @dhruv7827
    @dhruv7827 9 місяців тому

    What is that tool that is suggesting you the code? Is it an extension?

    • @harag9
      @harag9 7 місяців тому

      Co-Pilot. It costs per month to use, not sure how much.

  • @cezarygrzanka4229
    @cezarygrzanka4229 9 місяців тому +2

    4:10 and now... you just receive mail that some routes has to be wrapped in other component, that some of them may be exact, and for some reason to one of them you have to pass params. I think you just unnecesary complicated quite simple part od code just to reduce couple LOC 🤔

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      Again, you can create as many hypotheticals as you want. I reviewed this for this scenario, which is valid

  • @captsiro233
    @captsiro233 9 місяців тому +1

    Why do you have vim plugin if you are still using mouse... I don't have vim plugin and I use my mouse less.

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      It's not a competition 😅 to each their own

  • @Phooenixsx
    @Phooenixsx 9 місяців тому

    Hi good video , can u share u theme color of js code? ? thanks

  • @marcossequeira5433
    @marcossequeira5433 8 місяців тому

    It could be a better solution use an AuthGuard component and pass as childrens all the routes that you want to be protected?

    • @cosdensolutions
      @cosdensolutions  8 місяців тому

      depends how the component is structured. Maybe it doesn't allow this this way. But worth a try

  • @isaacjon
    @isaacjon 9 місяців тому

    U said that we cant use state in a custom hook. What does that mean? U just used useEffect and useState hooks in this custom useGeneretaeUrl hook.

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      Hmm, where did I say that? You Def can use hooks in custom hooks!

    • @isaacjon
      @isaacjon 9 місяців тому

      ​@@cosdensolutions9:45 can you check and explain it please

    • @samansaeedi1498
      @samansaeedi1498 9 місяців тому

      He says you CAN, and that's the beauty of it

    • @isaacjon
      @isaacjon 9 місяців тому

      @@samansaeedi1498 ahh i got it. It sounded like (can't)

  • @SacrificialGoat94
    @SacrificialGoat94 9 місяців тому

    Isn't sticking the access token in the search params a horrible idea?

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      you would usually put it in the headers of the request

    • @SacrificialGoat94
      @SacrificialGoat94 9 місяців тому +3

      @@cosdensolutions Really sherlock? Yet you did not mention that while creating "Senior level code" perhaps you're not quite ready to be making such claims.

  • @gustionusamba90
    @gustionusamba90 9 місяців тому

    What is the theme and font do you use?

  • @kirillvoloshin2065
    @kirillvoloshin2065 9 місяців тому

    got to propose to switch to TS

  • @ooorayooonyoooo
    @ooorayooonyoooo 10 місяців тому

    what is your color theme mate?

  • @icoderdev
    @icoderdev 10 місяців тому

  • @WolfamStart
    @WolfamStart 9 місяців тому +5

    Where are the tests, to prove you don't change the functionality?

  • @ask43242flight
    @ask43242flight 9 місяців тому

    Do you have a tutorial that shows how to embed JavaScript code within HTML(i.e. JSX)? I don't have solid knowledge to know when I should use () and when I should use {}. Basically, I highly depend on VSCode to help finding issues for me while I am write JSX code. Thank you

    • @cosdensolutions
      @cosdensolutions  9 місяців тому +1

      Hmm not specifically, but in every video I kinda do that 😅 it just comes with time! So keep practicing

  • @tauraamui
    @tauraamui 9 місяців тому

    not related, but I've never seen someone using VIM or the VIM plugin on an editor but completely defeat the point by just using the mouse, it's painful to watch

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      Well, what can I say.. I'm sorry you feel this way 😅

  • @jotasenator
    @jotasenator 9 місяців тому

    8:04 🤕

  • @savire.ergheiz
    @savire.ergheiz 9 місяців тому

    There is no such things as bad code. Any senior engineer always know that fact.
    There are only codes that carelessly being made due to many reasons.
    If you said its a bad code then how you justify those bugs that always goes into production no matter how good or big the companies behind?

  • @helios8567
    @helios8567 8 місяців тому +1

    you did the code better, but it's stil crap. You could do this code a lot more cleaner. Not a senior level imho.

  • @john_dren
    @john_dren 9 місяців тому

    I found it funny how the refactoring takes you like 5 min tbut a junior like me half a day or a day :D

    • @cosdensolutions
      @cosdensolutions  9 місяців тому

      hahaha it comes with time! keep at it 🤙