Feature/#83 setting validation #165
Merged
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
…h showing a simple warning or error, when an Exception is throwed, it won't assign the value, took only the CheckBoxSettingView.axaml for first version into account
…which is an indicator whether the method call comes directly from the user or the application
hendrikmennen
approved these changes
Jan 25, 2026
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.
#83
TitledSetting. The first version only shows validation warnings/errors for theCheckBoxSetting.AdvancedComboBoxSearchSettingISettingsServiceNote for validation logic: When throwing an exception inside the validator class, it is possible to intentionally prevent assigning invalid values to the bound property. This causes the behavior, if the view/vm is not in sync, that setting the previous value won't cause the setter to get executed. In this case the validation text was not updated. To solve this problem I added the InvalidateValidation command to the Checkbox. The drawback is, that the rule will be always execute twice. When extending this feature, other controls need to implement a similar behavior as well. Using the more standard way with
INotifyDataErrorInfois not simply possible due to architectural reasons.