[cms] Separate out CMS-level options from d3plus config in Visualizations #1216
Labels
effort: 2 - difficult
package: cms
priority: 4 - low
tag: breaking
Introduces breaking changes (minor or greater)
type: enhancement
Small, low-risk improvements
A number of hacky CMS-level configs are overloading the pure d3plus config, including:
We also want some new ones, like:
During the next database change, add a configuration column to handle these configurations, and move them OUT of the d3plus configs (but maintain backwards compatibility)
The text was updated successfully, but these errors were encountered: