I'm aware of using selectors in Redux, and make use of them. However I have a case where I feel that it would make more sense to store my newly filtered data in the store. Here's my example:
I have an app which displays lots of items. There is a "global filter" option that will only show a certain subset of these items.
The thing is, this filter is global. It changes this list of items across multiple pages and components (e.g. in a table, in a drop down menu). When the filter is set, as far as the whole app is concerned, the current subset is the only list of items that exist.
I could use selectors everywhere necessary but it feels like it would be more robust to just have a 'filteredItems' part of my store. What would be the disadvantage to doing this?
It's up to you to decide what state you have in your app, and where it should live. Yes, the common advice is to try to keep the store state minimal and use selectors to derive extended values from that, but there's nothing wrong with using reducers to create filtered values that are kept in the state. Your situation sounds like a perfectly reasonable use case for doing that.