Split reducers into different files, or change state logic

[leftmove]

Currently, wallstreetlocal uses Redux to manage all the complex, global state for different filers. This leads to a couple problems.

• All reducers are housed in a single, big file, and it is hard to manage them
• Things tend to get unorganized when creating new reducers, they should be more compartmentalized
• Performance can be slow when loading many reducers
• Lots of boilerplate, including complex, and perhaps unnecessary Redux logic

Redux settings probably need to be tweaked to implement more best practices. filerSlice.js is a big file, and loading it dynamically, if possible, could improve performance.

Or maybe the best solution is to abandon Redux altogethor, and adopt a new (or no) state library.

[shubham9069]

@leftmove I am new in this open-source world but I have a working experience As a Software developer so I want to make a small contribution to your vision can I be capable of doing it?

[leftmove]

Absolutely! Depending on your experience, this issue may be a bit complex and will take a while to understand.

Let me know which technologies you are most experienced in, and I can point you in the right direction.

@shubham9069

[shubham9069]

@leftmove I worked On MERN as well as had experience in Angular. you can checkout my portfolio which gives me brief explanation of me and my work https://shubhamkaushik-portfolio.vercel.app/

[leftmove]

@shubham9069

It seems you are a seasoned React developer; this gives you a couple of options depending on what you want to dip your toes in.

• This issue requires fairly in depth knowledge of Redux.js - a state management tool. I would not recommend it unless you really want to learn all about Redux (especially since many other state management libraries are trending up nowadays).
• Create charts. This is the issue I would recommend the most to you. Basically, you have to take in data and use your knowledge of JavaScript and React to create charts for that data. It would be good practice for any React developer.
• Migration to Next.js app router. This is the easiest but most tedious issue; I would also recommend it. Basically, you just have to update all the dependencies and get the entire app running on Next.js's newest version. It will require lots of refactorings, but there are many guides.

Whatever you choose, please let me know and do not hesitate to ask for help. I'll assign you as soon as possible and give you some tips to start off.

Thank you!

[shubham9069]

@leftmove I understand your concern but redux is also built on top of content API and I have prophecy in state Management using Context API. and second yeah I Would Love to contribute other 2 tasks

[mustafa-tola]

I would love to work on this task as i have previously worked on redux

[aadarsh10c]

Hey @leftmove , looks like person assigned this issue is not working, i would like to contribute to this issue. Please assign me this issue

[leftmove]

@mustafa-tola @aadarsh10c

Sorry for the late reply, have at it.

[mustafa-tola]

@leftmove i have done some work regarding this issue how can i test it sorry for the delay

[leftmove]

@mustafa-tola Easiest way to test is to run the front-end with npm run dev and make sure all the components are working.

[mustafa-tola]

@leftmove i have splitted the reducer into 3 different slices. Now i want to push it so that you can check if it is working. how can i do it. i have checked on my side. it is working but i want to cross check with you.