Exclude expression validations from backend #1571
Merged
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
I noticed that the expression-validation tests were a bit flaky, and it turns out I forgot to exclude expression validations from the backend in the original PR 🤦 . This was not an issue in normal use since the frontend and backend seem to always agree on what is valid and what is not. But it looks like there are some subtleties when it comes to saving delay triggering single field validations and repeating group triggered validations that could cause a mismatch if the order of requests was unlucky, due to cypress being very fast. This should hopefully fix the flakyness.
Related Issue(s)
Verification/QA
kind/*
label to this PR for proper release notes grouping