Closed aaronmccall closed 5 years ago
hey @aaronmccall! :)
Sorry, I'm feeling a little daft here... what does this let you do that you can't currently?
Hey Henrik!
My primary use case is when I have a slice of state for a thing, recipes, say, and I want to use createAsyncResource bundle for managing a searchable, sortable, filterable list of recipes inside that slice of state. So, my path would be state.recipes.list for that async bundle.
The current implementation doesn’t allow me to redefine the path that the root selector pulls its state slice from, so I end up with state.recipes AND state.recipeList.
Does that make sense?
On Sep 18, 2018, at 21:29, Henrik Joreteg notifications@github.com wrote:
hey @aaronmccall! :)
Sorry, I'm feeling a little daft here... what does this let you do that you can't currently?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
@aaronmccall just merged and released as part of 22.2.0
, thanks!
This allows much more flexibility for bundle composition.