docs: clarify that new validation mechanism is disabled by default #17072
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mshabarov
requested changes
Jun 21, 2023
| * integrating client, constraint, and binder validation into a seamless chain. | ||
| * A property that enforces full experience validation for Flow components. | ||
| * <p> | ||
| * The full experience validation integrates client, constraint and binder |
There was a problem hiding this comment.
I'd propose change it to "... integrates web-component's own validation, server-side component's constraints and Binder validation into a ...".
mshabarov
approved these changes
Jun 21, 2023
|
Kudos, SonarCloud Quality Gate passed!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The PR clarifies in JavaDoc that the new validation mechanism is disabled by default in Vaadin 14.
A follow-up to #17056
Type of change