-
Notifications
You must be signed in to change notification settings - Fork 321
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
Please spare some time to work on the version control and the documentation #873
Comments
@YoungWoong-Cho I'm sorry for that. Nevertheless there are some items of your issue not clear to me, I'm sorry again.
The
Also here it seems something related to Chart.js and not to the plugin. Anyway a sample with the code could help, I guess.
Is this issue related to annotation type or chart one? Here I can try to do some tests and see if
The chartjs-plugin-annotation doesn't touch anything related to grid or ticks. I think you are referring to Chart.js behavior. Anyway a sample with the code could help, I guess.
You are referring to
To evaluate if it's a bug or not, could you share the annotation config you are using? When you write "text box" is not clear if you are using a All options of the annotation plugin have got a default therefore it sounds weird that you should define all options. |
When all I want to do is overlaying a simple annotation on a plot,
chart js will still be asking me tons of configs to fill in -- which is hella tedious.
.
.
.
Config file
Different versions of config file
Config object looks atrociously different from version to version, and I can't find a friendly documentation about different
versions of config objects nowhere. What's the difference between
x
andxAxes
?Exception handling and type mismatch
Exception handling is also terrible. Only after I add some elements to the config object it complains about type mismatch, giving me something like
which is stupidly long and hard to read.
On top of that, when I google the error message, there's literally NILL useful answer that I can adopt.
Also, the type management is terrible. I had to use a syntax like
type: 'line' as 'line'
. JUST LET ME UES A SINGLE STRING VALUE..
.
.
Unexpected behavior
mode = 'vertical'
and specify the value, it gives me a linear line from bottom left to the top right. Why this behavior? At least provide me some useful message that helps debugging..
.
.
There are a lot more to be complained about, but I don't have more time to waste.
Please, please take some time to work on the documentation.
The text was updated successfully, but these errors were encountered: