Validation with multi error messages for a unique field

[pinonpierre]

Hi,

On Vaadin 8.0.5

I need to have validation with multi error messages for a unique field but for now, only one error can be emit for a field (In Vaadin 7, there was possible)

If the field has more that one failed validator, only the first error was displayed

Regards,

[Legioth]

Because of the way Binder allows defining validators both before and after converters are run, it would not be feasible to run all validators, and the converter might not support converting invalid input into something that could be passed to later validators. To avoid confusion, we're instead always only running until the first failing validator regardless of whether there are converters in between or not.

To work around this, you can define one big validator that internally collects errors from multiple "sub validators". The framework could also provide some kind of helper for making it easier to implement a validator that delegates to multiple validators and collects all messages.

[pinonpierre]

In some framework, we can indicate on validator itself if next validator must be executed.

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!