wip: async validation! #61284
Merged
wip: async validation! #61284
Conversation
This file contains hidden or 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
mmalerba
approved these changes
May 12, 2025
kirjs
reviewed
May 13, 2025
|
|
||
| readonly errors = computed(() => [ | ||
| ...this.syncErrors(), | ||
| ...this.asyncErrors().filter((err) => err !== 'pending'), |
There was a problem hiding this comment.
I think we already filter by pending on line 371?
| @@ -73,7 +83,7 @@ export class FieldLogicNode { | ||
| // Merge standard logic. | ||
| this.hidden.mergeIn(other.hidden); | ||
| this.disabled.mergeIn(other.disabled); | ||
| this.errors.mergeIn(other.errors); | ||
| this.syncErrors.mergeIn(other.syncErrors); | ||
|
|
There was a problem hiding this comment.
should we merge async and tree errors as well?
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information