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
I think it's not cool when you run your code and see that your chart looks different compared to the same one in Chart.js docs - then it takes time to find out how to reset the styling to customize the way you want...
The text was updated successfully, but these errors were encountered:
It's not a problem, that's rather a matter of taste and to me, it seems to be an unexpected behavior for a wrapper. Basically I'm ok with default styling and in particular it took some time to find out why grid lines are not getting displayed.
I see this as a problem, it took me a good time to figure out what I was doing wrong because the gridLines were not showing, and everywhere in the official docs the gridLines are showing without any configuration. So I searched this and found that it gets overwritten and it's not exposed in the docs or anywhere else.
It's really not a good idea to override default configuration in a wrapper when you depend on the official docs that explicitly says that the display property of the gridLines are true by default (and any other prop that might be overwritten as well).
Or at least make it clear in the docs that you are overriding it (I had to search in source code), so when people see things are not working the way they expect they will quickly figure out that some styles are being overwritten.
Why default Chart.js styles are overridden?
I think it's not cool when you run your code and see that your chart looks different compared to the same one in Chart.js docs - then it takes time to find out how to reset the styling to customize the way you want...
The text was updated successfully, but these errors were encountered: