I found out that in the Meteor-React-Redux stack we have to maintain the state of the user interface (e.g. filter update) and the domain state (e.g. getting data from Mongo collections) are separate things .
But there is an interesting case for managing an account (user), I think.
Now I get user information through Meteor.user()when subscribing to the collection (for example, the toDo list). While we are talking about the state of the domain (correct me if this is a false assumption!). But then I need to transfer user information to other components as a props (for example, up to toDo items, where I need user information for anything).
So, essentially, I came back (at least for this part of my application) to pass things as props (now it’s good, but if the application grows, it is tiring). This is exactly the kind of problem Redux will try to solve by putting it in this repository.
So my question is:
User Information: To save or not save Redux to Redux repository (i.e. pass down as props)?
* I also need to do this for the toDo elements themselves. That is, I am making my toDo objects with something like:
toDos.map((toDo) =>
<ToDo
key={toDo._id}
toDo={toDo}
/>)
However, I see no way around this.
alamo source
share