We probably want to file an issue about re-checking all this, as I know some of the original issues I believe were fixed in the underlying behaviors package, but I think we still do some extra logic here.

Probably a thing where when we can better test these and shore that up, we could try removing the intermediate class and see what happens or if anything breaks. (Assuming we have enough coverage)

Originally posted by @michael-hawker in #20 (comment)

Related Toolkit Discussion: CommunityToolkit/WindowsCommunityToolkit#3856

with specifically more prior context and links here: CommunityToolkit/WindowsCommunityToolkit#3856 (comment)