Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cms] Separate out CMS-level options from d3plus config in Visualizations #1216

Closed
4 tasks
jhmullen opened this issue Jun 9, 2021 · 1 comment
Closed
4 tasks
Assignees
Labels
effort: 2 - difficult package: cms priority: 4 - low tag: breaking Introduces breaking changes (minor or greater) type: enhancement Small, low-risk improvements

Comments

@jhmullen
Copy link
Collaborator

jhmullen commented Jun 9, 2021

A number of hacky CMS-level configs are overloading the pure d3plus config, including:

  • Tabs
  • Mini vs Large

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)

@jhmullen
Copy link
Collaborator Author

Closing this, replaced by #1293 in reports

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: 2 - difficult package: cms priority: 4 - low tag: breaking Introduces breaking changes (minor or greater) type: enhancement Small, low-risk improvements
Projects
None yet
Development

No branches or pull requests

1 participant