I'm currently developing an application and I'm facing a challenge in implementing Redux effectively in this particular scenario. Unfortunately, due to restrictions at my workplace, normalizing data is not an option.
Let's consider the following 3 views:
1) Displaying a list of folders (retrieved from an API, therefore using a single reducer for this entity).
2) Showing the details of a folder which includes a list of another entity - cats. Additionally, there is a filter form for cats.
3) Viewing a list of cats (similar to the second view but without the folder details). There is also a cats filter form present here.
How should I handle the cats state for both the second and third views? Should I create separate actions like "GET_CATS_FOR_FOLDER" and "GET_CATS" for each respective view (which may not be ideal)? Is there a way to consolidate these actions into one common action? The same question applies to managing the filter form that impacts the cats state.
Thank you in advance!