Is your feature request related to a problem? Please describe.
Someday we'd like to separate small parts of the core code to their own package. I notice the @router/route.bindings module knows too much about the @store/utils module. I'm not sure if this represents a problem right now, but it's starting to ring a bell.
Describe the solution you'd like
We need an accurate and simple way for the Resource component to call the route bindings using imported utils, instead of the router knowing where those utils can be found.
Describe alternatives you've considered
I imagine Resource importing a set of store utils and passing them to the createRouteBindings. open to discussion.
Is your feature request related to a problem? Please describe. Someday we'd like to separate small parts of the core code to their own package. I notice the
@router/route.bindingsmodule knows too much about the@store/utilsmodule. I'm not sure if this represents a problem right now, but it's starting to ring a bell.Describe the solution you'd like We need an accurate and simple way for the
Resourcecomponent to call the route bindings using imported utils, instead of the router knowing where those utils can be found.Describe alternatives you've considered I imagine
Resourceimporting a set of store utils and passing them to thecreateRouteBindings. open to discussion.