-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[iOS] Avoid CheckBox memory leak #16376
Conversation
Do we need the API change? shouldn't it be nullable?! |
@@ -30,5 +43,31 @@ public async Task UpdatingCheckBoxBackgroundColorUpdatesBackground(string colorS | |||
|
|||
await ValidateHasColor<CheckBoxHandler>(checkBox, color); | |||
} | |||
|
|||
[Fact(DisplayName = "Does Not Leak")] | |||
public async Task DoesNotLeak() |
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.
@jonathanpeppers does it make sense to standardize these tests? These are all basically the same format yea? Can we just use InlineData or a class to provide all the control types and just permutate through them all?
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.
I can do that after the current round of PRs are in.
It could probably be a parameterized test in MemoryTests.cs
, as long as the test is reasonably searchable/runnable in the device tests menu.
Right, changed. |
Description of Change
Avoid CheckBox leak on iOS.
