Skip to content

* Use pattern matching where possible (V110) - #620

Merged
PWagner1 merged 2 commits into
alphafrom
V110-619-other-issues-use-pattern-matching-where-possible
Sep 30, 2026
Merged

PWagner1 merged 2 commits into
alphafrom
V110-619-other-issues-use-pattern-matching-where-possible

Conversation

@PWagner1

Copy link
Copy Markdown
Contributor

Refactor null, type, boolean, and range checks across Extended Toolkit modules to use modern C# pattern matching. Also correct minor animation documentation wording and record the #619 change in the changelog.

Refactor null, type, boolean, and range checks across Extended Toolkit modules to use modern C# pattern matching. Also correct minor animation documentation wording and record the #619 change in the changelog.
@PWagner1 PWagner1 added this to the Version 110 milestone Sep 25, 2026
Clean up nullable annotations and null-forgiving operators across Extended Toolkit controls, rendering, forms, notifications, grids, and updater components without changing runtime behavior.
@PWagner1
PWagner1 merged commit d01cab1 into alpha Sep 30, 2026
1 of 5 checks passed
@PWagner1
PWagner1 deleted the V110-619-other-issues-use-pattern-matching-where-possible branch September 30, 2026 10:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant