-
Notifications
You must be signed in to change notification settings - Fork 637
Exporting INIT_PATH constant #96
Conversation
So we can use this action type in reducers
|
Do you have an example use case for this? When we added it we didn't intend for it to be used in reducers. |
|
I'm using it to modify state according to action.payload.path value. Maybe the action.payload is not intended to be used externally (?) |
|
You should use |
|
Yes, I do. The problem is getting the initial value and my idea was simply using |
|
Good point, @tonovotny. Actually, looking at the code now I'm not entirely sure we need |
|
I'm at a work week right now and things are crazy busy :( I think I can find some time today to take a look though. No comments yet! |
|
@jlongster 👍 If you've got some time, focus on #93. That's the only thing left for a 1.0. The rest we can get into later versions. |
|
I actually think it's fine to listen for |
|
I'm in favour of |
|
I like small API surface too but would prefer unambiguous solutions, so |
|
Any examples of use cases where init is important, instead of just listening for update? |
|
If we compare these two tests I find it natural for |
|
Closing in favor of #97 |
So we can use this action type in reducers