Stefan Dirix

Hi @manju2791, no update yet. However I think the best way to implement this feature would be via [JSON Forms middleware support](https://github.com/eclipsesource/jsonforms/issues/1670).

Hi @Ketec, this is very hard to diagnose for me without any further information. Note that we do code coverage tests in Angular Material just fine, using [`karma --coverage` ourselves](https://github.com/eclipsesource/jsonforms/blob/d65d7eb8a5050c6de7a4e086e01237bd2488f64c/packages/angular-material/package.json#L45)....

So would raising the target to `es2015` in JSON Forms fix the problem for you? Seems weird that this would cause problems only for code coverage testing.

But ES5 breaks the newer library? So would your problems be fixed if we switched to ES2015 and karma coverage?

Hi @Ketec, so all we need are some additional decorations? That's fine with me if they don't break anything. Would you be willing to contribute this?

It's not really a custom webpack build but just [invoking pure `ngc` with a config](https://github.com/eclipsesource/jsonforms/blob/d65d7eb8a5050c6de7a4e086e01237bd2488f64c/packages/angular-material/package.json#L37).

Hi @CarlosGomez-dev! Thanks for the feature request. In general this definitely makes sense, so if we could add this feature in a non-disruptive way then I'm definitely for it. Can...

Hi @CarlosGomez-dev, sounds good to me! I'll discuss with the team and come back to you next week.

Hi @CarlosGomez-dev, we very much would like to see this feature. So if you have time a PR is very welcomed! Regarding the implementation we're wondering whether it should be...

Hi! The use of lower level inputs has historical reasons. Originally the `cells` renderers were mandatory and not only used in Tables but reused in all control renderers. At some...