Ping @dgt41

@degobbis Please don't add a flag for the error class. You can achieve the same goal by copying the javascript files from /media/system to your templates/template-name/js and change the classes directly in the script (that's the reason Joomla has overrides)

@dgt41 In my opinion the template developer is not responsible for the form validation and the normal user should not deal with it. As a developer of a form extension, I try to render the outputs for all frameworks. Because it makes sense to pass the appropriate classes for the validation. In the end, it makes the lives of the developers easier.

This is supposed to be a framework agnostic helper. So adding hooks for framework specific things seems like a step backwards.

I do not understand your argument. To use a hard-coded class, which is not used in any current framework, I consider to be a step backwards. With this change I hope to integrate the same flexibility as has already happened with Modal.

I don't think that this is the right approach @degobbis - as mentioned in our Glip chat, you are trying to let extension devs fix what template devs broke. As a template dev, I should make sure that my template has the necessary stuff (=overrides or CSS) to make the generated markup look right - if I fail, it's my fault and not the extensions devs task to fix this.

@SniperSister You are not wrong, but unfortunately this lack falls back on the developer. It was worth a try.