Stefan Dirix

@DBosley Thanks for the extensive write-up, this is very helpful! Did you also manage to get the schema-based [rule support](https://jsonforms.io/docs/uischema/rules) working?

Hi @andresgutgon, thanks for the suggestion. This could definitely be added to each renderer set. > we could think about adding this to the JSON Forms core so any renderer...

You can use the translation like this, however usually I would expect people to use the `translate` function instead of the `translateError` one. The default `translateError` makes heavy use of...

> Ok I remember why I went with `translateError` the context of the error is not present the [original translateError](https://github.com/eclipsesource/jsonforms/blob/master/packages/core/src/i18n/i18nUtil.ts#L29) therefor I can't access `error.params` as I do overriding it...

Not yet right? The PR only added `placeholder` support for text and textarea cells. However placeholders could also be supported for example for number inputs.

Hi @zeroamps! This looks good! Would you be willing to contribute this renderer including a test case?

Hi @ajturner, we currently don't plan to implement or maintain a renderer set based on Stencil JS. Of course you can still reuse `@jsonforms/core` and implement one yourself. If you...

Hi @skawian, sounds very cool! At the moment we don't plan to maintain another binding or renderer set as part of the official JSON Forms project. However we can take...

Thanks for your interest in JSON Forms. Note that the errors are already passed down to the renderers as they need access to them to render the error messages. We...

Thanks for the detailed information. I updated the issue accordingly. Note that we have a lot of stuff planned for the next releases, so this issue might not be worked...