Anybody out there know the value of Redux Toolkit other than to make my life harder and drive me insane?
No cache invalidation. I can refetch but then I need to track when you refetch even when I navigate away and change back so what's the point? Why do so many "helpful libraries" feel like they only end to piling on complexity?
They end up adding these granular options which yeah sure fine but sometimes I want to just be like "don't do the caching" which seems like the obvious initial thing but there's not that option so I have to find the granular setting somewhere.
Maybe my brain just doesn't with however this thing was designed but the setup and usage seem overly complex for every query/fetch or whatever you want
My guess is that Redux was the original thing and so it's stuck the way it was originally created and everything after that is connected to the original decisions.
I tend to find more recent state management tools to be designed in an easier to use way. Xstate or pinia from Vue
@elephino I mean, it’s way nicer than the old way.
Are you talking about the query part?
(I haven’t really tried any newer state libs, and have been using react query…. but have been thinking of trying out redux query because I read a couple of folks say it’s kind of ok now)
@renedudfield yeah the query stuff. Seems telling that someone before me made a hook wrapper for the hook that comes out of one of the query apis created by the library.
I keep thinking, "is it me? Have I lost my ability to reason about making queries?"
@renedudfield I'm going to say it probably works great for some people.
I think if I worked in this repo all the time I might be really adept at using this tool. Should it be that way? Not in my opinion, no. But, as with most decisions in codebases, this decision wasn't made by me and I still need to live with it
I'm sure someone out there at a previous company I worked at is looking at a git blame and cursing my name
Charlie Triste
René Dudfield