fix(formvalidation): no error for missing field on autocheck #2901
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
lubber-de
added
type/bug
lubber-de
added
state/awaiting-docs
|
Docs added by fomantic/Fomantic-UI-Docs#499 |
lubber-de
added
state/has-docs
lubber-de
added a commit
to fomantic/Fomantic-UI-Docs
that referenced
this pull request
May 10, 2024
Added new ignoreMissing parameter as of fomantic/Fomantic-UI#2901
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
A followup on #2633
As we centralised the field getter, the error message of a non existing field will occur all the time, even in situations where we definately want to remove field related validation rules if a field is non existing anymore and are aware of that.
Testcase
Broken
https://jsfiddle.net/fgw1bqr0/3/
Fixed
All fine, no errors
https://jsfiddle.net/lubber/3725m4o1/1/
Closes
#2577 (comment)