Closed cluzier closed 1 year ago
See PR #376
See PR #376
Is there a fix for those of us who are using TS? I read through the comments but doesn't seem like there was any sort of solution.
See PR #376
Is there a fix for those of us who are using TS? I read through the comments but doesn't seem like there was any sort of solution.
The both PRs are going to apply the same change which is a workaround to solve the issue #374. Therefore the answer is yes but there are some doubts if this change makes really sense (setting default type) or if not better to fix it (if possible) in main repo of Chart.js.
@cluzier the issue is not related to the plugin but is in CHART.JS. See comment https://github.com/chartjs/Chart.js/issues/11288#issuecomment-1561777505 and PR which is fixing this issue: https://github.com/chartjs/Chart.js/pull/11309
The bug fixing will be released in next CHART.JS version and nothig to do in datalabels. I think you could close this PR.
@cluzier the issue is not related to the plugin but is in CHART.JS. See comment chartjs/Chart.js#11288 (comment) and PR which is fixing this issue: chartjs/Chart.js#11309
The bug fixing will be released in next CHART.JS version and nothig to do in datalabels. I think you could close this PR.
Thank you for clearing this up for me!
This pull request addresses an error in the code by making the datalabels property optional in the PluginOptionsByType interface. The change allows for more flexibility in configuring the datalabels plugin for different chart types.
Changes Made:
Testing Done: