Skip to content

Conversation

@reck1610
Copy link

Description of Change

Support null values in NumericValidationBehavior.

Linked Issues

PR Checklist

  • Has a linked Issue, and the Issue has been approved(bug) or Championed (feature/proposal)
  • Has tests (if omitted, state reason in description)
  • Has samples (if omitted, state reason in description)
  • Rebased on top of main at time of PR
  • Changes adhere to coding standard
  • Documentation created or updated: https://github.com/MicrosoftDocs/CommunityToolkit/pulls

Additional information

@reck1610 reck1610 force-pushed the numeric-validation-behavior-support-null branch from ca5404d to a983ba3 Compare September 12, 2025 09:50
@reck1610 reck1610 force-pushed the numeric-validation-behavior-support-null branch from a983ba3 to 6835d75 Compare October 8, 2025 08:40
@dotnet-policy-service dotnet-policy-service bot added stale The author has not responded in over 30 days help wanted This proposal has been approved and is ready to be implemented labels Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

help wanted This proposal has been approved and is ready to be implemented stale The author has not responded in over 30 days

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] NumericValidationBehavior crashes when bound to nullable numeric types (e.g., decimal?)

1 participant