วีดีโอ

Waiting for next❤

We need more videos like this, sir

Great video, thanks! One question I have is that I’m surprised that the react-query docs and this video don’t abstract the queryFn into one reusable function that can take the path and request options (and using axios.request and specifying the method in the request options) instead of creating a new api request function for every new hook (e.g. getMe, getUser, etc). Is this because these guides want to keep it relatively simple or is there a downfall to that kind of architecture (ie abstracting the request into one function)?

This is absolute gold. Waiting for the course

Who loves hearing him say, 'The solution?'

good tips, I'm gonna apply them to my projects

perfect video. may i ask share your code github link?

Thank you very much!! This is amazing, is there a book or good resources for understand more about clean React Architecture?

This is actually really good. I have seen tons of tutorials, but none of them actually go over how to structure your application, best practices, refactor, etc. It would be nice that for a course to start from scratch to advanced for both beginners and experts. He actually go overs the bad first and then refactors it. It's a little rush, but if this guy can create a course from scratch to advanced in react, he would be an awesome teacher. I have not seen this.

There is a library called react-ioc which can be useful to reduce some of the stuff in react... Do take a look

I wonder why using a Map instead of a Set to store checkedByIds , since it’s just a list of unique strings?

didn't know we were doing tbd. nice vid.

looking foward to the course

Thank you, nice video I liked it

This is super interesting, I hope you upload more videos like this implementing architecture and good practices

Like and sub

The best tutorials. All comes from years of awesome work experience. 👏

video editing nice and clear 👍

Don't you think it is possible to try to have a structure that allows more colocation? I think in that case it would be easier and more straightforward to navigate the repository: for example, if I need to make changes or check some details of the "user," I know that I will find everything within the "user" folder, from the "infrastuctural" parts down to the "domain" parts

Hey can you teach how to setup vite like you setup repo

As an intern, until now I was confused by why the queries were all react hooks and how it worked. Thank you for this amazing video, perfect timing!!!

I don't know how much attention you get on these, but I really look forward to each one you make! Like, seriously great content man. You don't see this sort of stuff anywhere else :)

Amazing series

Is there a reason why you used the class based approach for dependency injection in the video compared to the pull request where you have just passed the api as a dependency to each service function? IMO the approach in the video looks cleaner. Im just curious what your thoughts were about that. This video series is really amazing. Thanks for that :)

Keep it up 👏🏻

The traceability is bad here and not all the logic need to be extract to domain layer

Nice video! Are you German?

2:45 - I disagree about using refs to access the dom in 2024. Ref access was Reacts way of hiding their performance issues back in the day. But dom access is fine now. 10 years later good grief.

Great video as always mate! Keep up the good work. Thanks 👍

Another awesome video tutorial for the ones who are seeking how to become clean coder. I love clean coding videos and security practices in coding. ❤

Pleas make video for unit testing

This is not in the playlist

I think another disadvantage is, when you get into increasingly difficult scenarios, it leads to more and more abstraction. And so it becomes harder to come up with a function signature that upon reading explains what's happening. Because it's so abstract from the layers doing the work, there could be 20 different ways to achieve what your function is stating it does. And I don't think turning your function name into a sentence changes that either. Where when you work under locality of behavior, your what and how should be in the same place, and so it becomes easier to figure that out.

is domain the same as services?

Do you keep your react query useQuery hooks and data fetching functions in the infrastructure layer or domain layer? Amazing video, like others have said you're actually explaining things have meaning to people and teach people good principles.

Please continue these kinda videos, especially naming the variables, functions, pages, components, like infoPanel, infoContainer, infoWrapper, infoParent, infoBox etc for example if I'm using infoPanel, and I need a similar component name so what should I name it from above list? That would help

Would you not prefer a class for the User here rather than a file with methods etc.

These videos are amazing. I very much enjoy your calm explanations. Solid work!

I can only speak for myself, but after having a go at projects, this type of videos are much more helpful than most of the web dev content I've seen. Thanks!

learning alot from these series. I find these refactoring videos extremely helpful and insightful compared to alot of tutorials (everyone coded up in one go with minimal explanation). understanding why you made these choices and the tradeoffs involved was invaluable and will definitely apply to my own projects and work. Thank you so much for your amazing lessons

Very nice content ❤

question, isn't bad practice naming react components in kebab case?

How can we access the code ?

Just the perfect video for all react developers at all levels. Nice work. Waiting to see more great content.

Boom... subscribed!

I like the video however one thing to point out. That is not dependency injection, it's dependency inversion 😅 Dependency injection applies dependency inversion by dynamically injecting the implementations (or so i've been told). I cannot wait to see the vertical slice transformation. As of now the only difference i see is that we've moved from traditional react architecture to clean architecture and the layers are always the headache for any type of application. Rare content BTW

Great stuff!

thank you for all your efforts. These kind of videos are really rare. keep making these invaluable content!

Next level stuff, loved it. Thanks a lot.

Thanks for this content, I have one question, introducing classes would violate the functional programming nature of react, no?