In an ongoing project my team is building a new web application that relies heavily on a rest api. As we decided to try react we naturally came to implement redux and a middleware, as we've read this is the way to go. However, further into the project, we noticed it would be a good approach to bundle all the api related logic into a common library. So from that point on, the frontend (react) got isolated from the logic querying the api. Due to a tight shedule we kinda rushed through this transition, leaving us with lots of redux code implementing the new library.
The new library manages the complete interaction with the api and even abstracts it away through different objects representing information compiled from different endpoints.
The question is: do we even need redux with this kind of architecture? It feels like completely duplicating the amount of code required for simple actions, due to the need of actions, reducers and the store. I really feel like the library we created holds its own store and should therefore be consumed directly from within the react components. Would this be considered bad practice?
Recently we've created a module of the library, that provides boolean toggles for whether a component should be visible or not. I'd actually like to build them right into the components (maybe as props). I guess I'm blinded by buzzwords on this matter, please enlighten me.