Currently when you create a module via vuex-easy-firestore, it will add a bunch of actions, getters, mutations etc.
I'm thinking of creating a system where actions that you wish to use should be imported from the library and added directly to the vuex module.
This will improve code readability. No more actions which are added automatically, so it's easier for teams to understand the app architecture.
This will also improve treeshaking support, since just the actions you decide to add to a module and wish to use, are extracted from the library. Unused actions won't bloat your app unnecessarily.
Help requested:
I'm using a lot of getters, mutations, state props that are only used by my library internally.
If anyone can advice me how to best extract this logic and have it automatically imported when a single action is added to the vuex module, let me know!!!
A milestone for v2.0
Currently when you create a module via vuex-easy-firestore, it will add a bunch of actions, getters, mutations etc.
I'm thinking of creating a system where actions that you wish to use should be imported from the library and added directly to the vuex module.
This will improve code readability. No more actions which are added automatically, so it's easier for teams to understand the app architecture.
This will also improve treeshaking support, since just the actions you decide to add to a module and wish to use, are extracted from the library. Unused actions won't bloat your app unnecessarily.
Help requested:
I'm using a lot of getters, mutations, state props that are only used by my library internally. If anyone can advice me how to best extract this logic and have it automatically imported when a single action is added to the vuex module, let me know!!!