Instead of using Vuex, we should just have a module "state.js" that tracks all global state and houses functions for manipulating it. Use Vue.observable() to make state observable. In the future we can have global state for loading, use this central place to limit in-flight queries, cache lookups centrally, etc.
My only hesitation on getting rid of Vuex was the ability to view the current state via devtools. However, in webpack you can expose internal modules using output.LibraryTarget
Of course, we need to document where this data is exposed in a section about development and debugging.
Instead of using Vuex, we should just have a module "state.js" that tracks all global state and houses functions for manipulating it. Use Vue.observable() to make state observable. In the future we can have global state for loading, use this central place to limit in-flight queries, cache lookups centrally, etc.
My only hesitation on getting rid of Vuex was the ability to view the current state via devtools. However, in webpack you can expose internal modules using output.LibraryTarget
Of course, we need to document where this data is exposed in a section about development and debugging.