Allow setting a "global" null representation that skips other converters and validators in the chain

Legioth commented 7 years ago

It would be useful to have a feature similar to the current withNullRepresentation that would instead bypass all intermediate converters and validators if null is encountered from the model side or if the null representation value is encountered from the presentation side. In this way, it wouldn't be necessary to ensure that those intermediate steps also work with null values.

Spun of from #8321.

elmot commented 7 years ago

When implemented, please update @deprectated in: com.vaadin.v7.data.validator.NullValidator

stale[bot] commented 6 years ago

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!

jorndp commented 4 years ago

Hi,

I still have a usecase for this issue :

I have 1 Textfield binded with an EmailValidator. The email is not mandatory so user should leave it either empty or a validated result from the EmailValidator.

Some flag that null or empty is allowed would be very efficient for such use case.

Regards, Jorn

vaadin / framework

Allow setting a "global" null representation that skips other converters and validators in the chain #8465