Proposal: Severity types for addError about forms

[Unlink]

I don't understand your use case, why you need sometimes send warning and sometimes error? What is the difference between error and warning, in both cases is form invalid or how is it?

[juniwalk]

Hi, use case could be for example sign up form, if user exists I can send message on the username input with bootstrap warning color. It's matter of choice of how to handle my forms.

[JanTvrdik]

I don't get. If the username is already taken, it should be error, not a warning.

[juniwalk]

Alright bad example. Look - all I would like is to have same flashMessages implemented for forms too. It would add to consistency and give use more power over how we handle our forms.

[Unlink]

Yes, but i don't think that there is a reason, when you need something else than error in forms.
Field is valid or not. That's something different like a flash messages, their purpose is notify user about something (success, fail, info...) but in form, we need to show only validation errors.
I can't imagine use case, when is needed something else than error.

[juniwalk]

I see, well if giving us a choice is not good enough then I don't have anything else to say.

[Majkl578]

This sounds like a valid use case for client-side code (e.g. password is not strong enough as a warning), but I don't see any benefit in server-side validation...

[juniwalk]

Frankly I have no idea how client-side works, I am not that into javascript.

[jtojnar]

This would be nice to have. Currently, I am building custom Rules instance and attaching it to a data-form-warning-rules attribute:

jtojnar/entries@601b203#diff-4078d83a9a0ef325c67991359ddfe536R73

Then I handle it in JavaScript:

jtojnar/entries@601b203#diff-20ca0a4947ea7c1006cda82eca50397c