docs(readme): correct $error equivalence #1188
Open
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
As vuelidate#1046 suggests, `$error` is true when the form is `$dirty` and either `$pending` or `$invalid`.
|
@dobromir-hristov mind a quick review or merge? ❤️ Thank you for your continued support 🙏 |
|
@dobromir-hristov some time passed and given the recent activity on this repo I'd like to ask for a quick review / merge on this again 🚀 |
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.
Summary
As #1046 suggests,
$erroris true when the form is$dirtyand either$pendingor$invalid.Metadata
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
The PR fulfills these requirements:
nextbranchfix #xxx[,#xxx], where "xxx" is the issue number)