-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Clean up LocationManager warnings #13633
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
Conversation
I'd appreciate if we can reduce the changes of this PR to the minimum - would also allow this to be against the release branch. |
Absolutely fine, I was not sure about targeting since this wasn't an urgent fix. Would putting the Async updates in another PR be against release 10.x as well? |
IMO those should go against master |
On it :) |
Ratings-only changes pulled into #13639 |
Cleaned up the ConfigureAwait suggestions. Updated to current collection initialization pattern.
6ca7cc2
to
009b592
Compare
This PR now targets master with only the warning cleanups Strongly recommend using the hide-whitespace option when reviewing :) |
@Shadowghost this PR now only does the warnings changes (the other PR for 10.x has been merged)v |
This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged. |
This is now a NOP after resolving conflicts. Closing |
Changes
Fixed the warnings about missing
ConfigureAwait(false)
on the manifest stream processing.Updated to current collection initialization pattern in LoadCultures