How much state management is appropriate on a Dashboard?

[joedski]

A question to consider while learning this: How much state management is appropriate for this type of project?

There are a few options:

• Wing it: Just do whatever
• Event Bus / Global VM: Attach/inject a global Vue instance to use as an event bus and central store for cross-cutting concerns.
• Vuex: Fluxy store we all know and love, at least if you like Vue/Mobx-style reactivity.

A dashboard isn't quite a full on SPA, but at this point I've only dealt with SPAs and Content Sites, not so much Dashboards, so I'm not sure what's appropriate here. It seems however more like a Content Site than a SPA, and so either Wing it or Event Bus / Global VM seems like a more appropriate choice.

I suppose it depends on just how much data the different sections of the Dashboard are likely to share.

• Low data reuse would point to the former strategies
• Moderate or Higher data reuse would favor Vuex.

[joedski]

State to Manage

There's only a few pieces of state that I can think of to manage:

• Session, if that is not handled on the Client using cookies (for example, using JWTs)
• Whatever is local to a Section
  • The current Page's data
  • Messages/Notifications in the Side Pane
  • Such'n'So

There may be more, but as of writing this would seem to indicate that either Wing it or Event Bus / Global VM is the better strategy. Session is pretty cross-cutting, but can easily be handled using a combination of request enhancers and Axios instantiation.