Jukka Kurkela

It looks like the negative fill is not based on the origin, so that would be a bug in current behavior. For the desired behavior, the stacking would need another...

@iammemon when you replace the data and labels, how should Chart.js know what the relation of new data to old data? Labels? I think in this kind of use case...

I think this one is more related to the `beginAtZero`, that we already changed to default for true for bar charts. The `minBarLenght` correctly applies, its just not visible. ...

Anyway, it would still be feasible to have a visible bar when there is a value even when `beginAtZero` is false. `minBarLenght` could be used to figure out the amount...

So lets see if I understand correctly: - You have a .html (or equivalent) file referencing `chart.js` with `script` tag. - You have a TS project that you compile and...

Maybe you can use the `import type {Chart} from 'chart.js'` pattern to work around this? (I'm writing on mobile, so too hard to test)

It almost works actually: https://codepen.io/kurkle/pen/ZEXNgJW Just the dougnut controller expects all datasets to be dougnuts, and tries to call `_getRotation` from every controller, which fails.

@petronellius what would be a mandatory property? I don't think there is anything mandatory, because the options are backed by defaults from chart type and scale type.

I'm not quite sure how this should be handled. Should we aim to remove the `DeepPartial` for option types and mark everything optional, or should we export these kind of...

I'd guess this is because you are importing chart.js asynchronously and the adapter needs to be imported after chart.js The editing you did is wrong in many ways. After that...