Allow validation errors on entries without interaction #5594
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:
Implements a way to show errors without user interaction as described in the issue mentioned below. The main goal was to implement this change without modifying existing tests, ensuring that current behavior remains intact. The default functionality continues to work as expected without setting
AlwaysShowValidationError
.All the tests create their testbed from the ground up instead of expanding a single test and doing
SetText()
for example. This way the tests test the behaviour when the entry is rendered instead of relying on user interaction to tigger aRefresh()
.Fixes #5590
Checklist:
Where applicable: