I was actually looking exactly as I have big project and was thinking of using context for creating small chunks for each module, as project need to have modules(widgets) which user choose to have on screen (1-6 widgets at a time on screen) and can close and open other widget any time, but re-rendering is going to be an issue as I am getting data via web socket. Will go back to the redux solution what I initially thought. If you have any other idea please do suggest.
Hi, It's a bit difficult to suggest anything without better understanding, but generally I would advise that most scenarios can be handled with straight up react state and some prop drilling, if the components are structured well this may work fine. Personally I would struggle to find a good reason to use Redux (for projects that don't already).
@@RedhwanNacef Thank you, thinking of keeping redux for something like global data, which is needed for making api call and showing details in each widgets, and use redux to store data which is going to be coming from web socket(data changes every second) and will be handled better as redux is good at it like batch update an all. Apart from that rest other to use state and drilling props down to 1-2 level.
Cool stuff, hope it all goes well. I would recommend having a look at react-query (react-query.tanstack.com/) for api calls too if you haven't already.
Thanks for making this comparison. I've used Redux in most of my projects and wanted to quickly check the state of things. This helped a lot!
You’re welcome. Glad it helped!
Pun intended?
Thanks so much! this is the exact video I was looking for! now only if I could understand it ;)
You're welcome. Let me know if anything is still unclear, happy to try help.
Thanks buddy! great tuto!
No problem! Glad you enjoyed it :)
So good bro! thank you for the flow
Glad you enjoyed it, thanks!
good .clean .. simple .. you are really good
Thank you. I appreciate it.
I was actually looking exactly as I have big project and was thinking of using context for creating small chunks for each module, as project need to have modules(widgets) which user choose to have on screen (1-6 widgets at a time on screen) and can close and open other widget any time, but re-rendering is going to be an issue as I am getting data via web socket. Will go back to the redux solution what I initially thought.
If you have any other idea please do suggest.
Hi, It's a bit difficult to suggest anything without better understanding, but generally I would advise that most scenarios can be handled with straight up react state and some prop drilling, if the components are structured well this may work fine. Personally I would struggle to find a good reason to use Redux (for projects that don't already).
@@RedhwanNacef Thank you, thinking of keeping redux for something like global data, which is needed for making api call and showing details in each widgets, and use redux to store data which is going to be coming from web socket(data changes every second) and will be handled better as redux is good at it like batch update an all. Apart from that rest other to use state and drilling props down to 1-2 level.
Cool stuff, hope it all goes well. I would recommend having a look at react-query (react-query.tanstack.com/) for api calls too if you haven't already.
@@RedhwanNacef Thank you so much, I mean haven't heard about it before but looks promising.
where those description labels come from ? (callback, predicate, dependants . . . )
They are an IntelliJ feature called Inlay Hints: www.jetbrains.com/help/idea/inlay-hints.html.
I'd suggest getting a better microphone :)
I already have :) hopefully my latest videos are a bit better.
@@RedhwanNacef In my opinion the mic quality is fine :)