-
Notifications
You must be signed in to change notification settings - Fork 80
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
Fixing crash when setting empty string for SettingsCard's Header and Description #312
Fixing crash when setting empty string for SettingsCard's Header and Description #312
Conversation
@dotnet-policy-service agree |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Dub1shu Thanks, changes look good!
Why create a custom function? Can't use CS |
@Dub1shu I am assuming because of |
@Jay-o-Way |
Alrighty. Thought it would be string but I see 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added tests and confirmed that these changes fix the issue. Looks good, thanks!
Thank you for reviewing and adding the test 😄 |
Fixes #310
There was a crash when binding an empty string to Header or Description while the content of SettingsCard was set. This pull request fixes that issue.
PR Type
Bugfix
What is the current behavior?
When the content of SettingsCard is set, binding an empty string to Header or Description causes a crash.
What is the new behavior?
When the content of SettingsCard is set, binding an empty string to Header or Description will no longer result in a crash.
PR Checklist
Please check if your PR fulfills the following requirements:
Other information
I would like to explain the fixes in this pull request using XAML simplified for the SettingsCard: