You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current JSON config approach has a few issues:
It's also responsible for the layout
It can be difficult to edit manually
All config properties are top-level (as opposed to some options being for the provider, others for the charts). As a result, adding an option to the pie chart expands the top-level API surface area. Maybe this is an issue either way.
I'm trying to think of a way that v2 can make it easy to edit each chart's configuration, and be easy to use wherever -- in a dedicated dashboard page/site, or within your CMS (e.g. WordPress). I've got a few options so far:
The current JSON config approach has a few issues:
I'm trying to think of a way that v2 can make it easy to edit each chart's configuration, and be easy to use wherever -- in a dedicated dashboard page/site, or within your CMS (e.g. WordPress). I've got a few options so far:
Custom elements
Use the new vue custom elements plugin, the old one, or skate.js, or stencil.js.
Vue components anywhere
Instantiate vue on body or top-level div, and use vue components inline. Requires the runtime+compiler version of vue.
jQuery style
At page load, search dom for vizwit components and initialise vue on them. Requires the runtime+compiler version of vue.
Use as vue library
Vizwit will be consumed as a set of vue components, installed by npm, rendered into a consumer's SPA.
Serialised as JSON or YAML
Basically the current approach.
The text was updated successfully, but these errors were encountered: