-
Notifications
You must be signed in to change notification settings - Fork 87
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
tons of console errors #17
Comments
Yes, that is a bug in the library ApexCharts, I can't do anything about it unfortunately :(. You can ignore them. |
add an option to delete null points |
Seems like I've fixed it but I don't know what fixed it 😅. I don't have anymore those errors with the latest beta (and maybe even before that) |
I'm in the latest version and still seeing these errors (10's of thousands of them!) |
It happened again also on my side. It's not breaking anything, so I'll keep this opened. Maybe it will solve itself in the future while upgrading the library. |
In the latest beta (v1.11.0-dev.1), I've updated the apexcharts library to the latest version which seems to have fixed those console errors (at least there's way way less). Could you please check? |
just found this and updated and yes, I do believe the errors have disappeared ;-) thx! |
Cool thanks for the feedback :) |
made a dirty hack to get rid of most of the spam Log. Only drops an console error when leaving a page that contains an apex card. /www/communty/apexchart-card/apexchartcard.js !!!!!!!!!!!!!!!!MAKE BACKUP OF THE FILE!!!!!!!!!!!!!!!!!!! Use a unminify tool like to make it more readable: https://www.unminify2.com/ Line: 8661: Line: 23394:
|
Btw for those not comfortable editing the JS file. Attached here is a copy, replace in /homeassistant/www/community/apexcharts-card/apexcharts-card.js (rename remove .txt extension) WARNING its not minimized so slightly bigger than orginal (minify yourself) Reduces the spam a lot. |
Not sure now... Just did an empty cache/hard reload and now I see no errors....
The text was updated successfully, but these errors were encountered: