Make DisplayAlert & DisplayActionSheet more consistent by adding Async #28053
+249
−182
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
🚨 API change(s) detected @davidbritch FYI |
jfversluis
force-pushed
the
net10-displayprompt-noasync
branch
from
441e9bd to
a1e2853
Compare
jfversluis
force-pushed
the
net10-displayprompt-noasync
branch
from
a1e2853 to
55ed90d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
This adds the Async suffix to DisplayAlert and DisplayActionSheet to be more consistent with the rest of the codebase and following the guidelines from Microsoft. The (now) old methods, without the Async suffix, are marked as obsolete.
Issues Fixed
Fixes #6720