From 784a3b58a7ff816547961cb272e5f13bcc94332c Mon Sep 17 00:00:00 2001 From: Gerald Versluis Date: Mon, 24 Nov 2025 10:22:53 +0100 Subject: [PATCH] Update validation callback description Removed mention of exception handling for validation callbacks. --- docs/fundamentals/bindable-properties.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/fundamentals/bindable-properties.md b/docs/fundamentals/bindable-properties.md index d340d7249..e3bf14ec0 100644 --- a/docs/fundamentals/bindable-properties.md +++ b/docs/fundamentals/bindable-properties.md @@ -149,7 +149,7 @@ static bool IsValidValue(BindableObject view, object value) } ``` -Validation callbacks are provided with a value, and should return `true` if the value is valid for the property, otherwise `false`. An exception will be raised if a validation callback returns `false`, which you should handle. A typical use of a validation callback method is constraining the values of integers or doubles when the bindable property is set. For example, the `IsValidValue` method checks that the property value is a `double` within the range 0 to 360. +Validation callbacks are provided with a value, and should return `true` if the value is valid for the property, otherwise `false`. A typical use of a validation callback method is constraining the values of integers or doubles when the bindable property is set. For example, the `IsValidValue` method checks that the property value is a `double` within the range 0 to 360. ### Coerce value callbacks