score:1

Accepted answer

i like that you try to find your own solutions to your specific problems. it's the sign of an engineer, just in this case this isn't the solution.

i think the idea of how redux teaches you to do things is not intended to be canonized. you have the ability to put a dispatcher on your props because it allows things to be transparent, meaning that things are bound outside of your class and injected in. you have hidden your store dependency by directly referencing it in some other files. it's no longer as obvious how your application works with regards to the workflow. another react developer would be confused, i suppose that's the major downside.

if you're ok with those aspects what you're doing is fine. fine as in, it gets the job done, but not "fine" in that it embraces concepts like single responsibility principle


Related Query

More Query from same tag