Deepak Kumar

The previous way of Mixins worked well for ES6. However, it was not enough for Typescript. - We need proper type checking in Mixins themselves - the compiler needs to...

Yes, it feels really sad having to go back. Our usage is quite specific. So, I guess that we can try some simpler approaches as well. I will get back...

For example, if we suggest that users should always create an explicit ChartGroup object (i.e., empty or string argument is not allowed), then entire ChartRegistry and *All functions can move...

There are isolated variables here and there - like `uniqueId` keeps the last id, events trigger keeps the last event. However, I do not think anything major. I will keep...

With the recent work with ChartGroup and FilterStorage, I believe we can now move the entire ChartRegistry to the compact layer. For this, string argument for a group name will...

Since we moved to ES6, accessing any property is possible, which the current version will continue to allow. Through documented API, I think that we should allow read-only access to...

Can this be closed?

We may try https://esdoc.org/, looks promising. It supports coverage as well.

Sure, will do.

`esdoc` seems to be not actively maintained. https://github.com/esdoc/esdoc/issues/556 Let us hold migrating till the situation becomes clearer. Will remove the ES6 label.