-
Notifications
You must be signed in to change notification settings - Fork 11.9k
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
Per-controller options #5191
Labels
Milestone
Comments
Non-matching option names:
There's also a number with a different amount of nesting:
|
This was referenced Jan 27, 2018
Closed
Closed
Closing as implemented in #5999 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From discussion with @simonbrunel over Slack:
Mixed charts today don't work well because we have global options instead of per-controller options (see #4587 for more details). A possible solution would be the one below:
When creating / updating a controllers, we should resolve options from:
dataset.*
: per controller/dataset optionsoptions.*
defaults.{datasetType/chartType}.*
defaults.global.*
and store the result in a private
_config
variable in each dataset controller then controllers would not anymore look at thechart.options
values only refer tothis (the controller)._config
The options cannot always be merged automatically because the names don't match. E.g. global
showLines
vs. controller/datasetshowLine
. AndpointBackgroundColor
vselement.point.backgroundColor
It will be difficult to separate dataset options from attributes like
data
,_meta
,_children
and methods liketransition
andease
that are also defined on the datasetThe text was updated successfully, but these errors were encountered: