Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

don't provide custom class names #114

Merged
merged 3 commits into from
Oct 27, 2023
Merged

Conversation

stevenbrix
Copy link
Collaborator

@stevenbrix stevenbrix commented Oct 27, 2023

The WinUI runtime queries objects for class names when applying templates and styles. If you provide a class name that isn't recognized then it will fail to apply those properties. generally, custom types are all handled through code generated by the xaml compiler for you, but we don't have all of that machinery.

this regressed as part of #108. i really knew better considering the comment that i happily ignored (which i restored in this PR). past steve would be disappointed with me :D

@stevenbrix stevenbrix requested a review from a team as a code owner October 27, 2023 02:14
@stevenbrix
Copy link
Collaborator Author

stevenbrix commented Oct 27, 2023

I'm trying to figure out a test case. The previous code seems to be fundamentally wrong and I'm not yet sure how we ever got into the previous block. My hunch is that if I do some type erasion we may hit this. Will test the theory in the morning

@stevenbrix stevenbrix merged commit 108f24a into main Oct 27, 2023
1 check passed
@stevenbrix stevenbrix deleted the steve/fix-get-runtimeclass-name branch October 27, 2023 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants