-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[google_map_flutter] Fix map object regression due to async changes #4171
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
Merged
auto-submit
merged 10 commits into
flutter:main
from
stuartmorgan-g:maps-marker-regression-fix
Jun 16, 2023
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
6693a3d
Extract fake platform impl to a separate file
stuartmorgan-g 0c41040
Wire up a platform recorder
stuartmorgan-g 8b2580b
Update all map object tests to use the new recorder
stuartmorgan-g 4c0d146
Convert remaining test and remove old fake controller
stuartmorgan-g 7791289
Add new multi-update tests with fake delays
stuartmorgan-g 4ea63c7
Remove incorrect awaits
stuartmorgan-g 80f0354
Version bump
stuartmorgan-g 488becc
Merge branch 'main' into maps-marker-regression-fix
stuartmorgan-g 3faf721
Merge branch 'main' into maps-marker-regression-fix
stuartmorgan-g a4c502c
Add a dependency override in the web example
stuartmorgan-g File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
Do you have any idea on what can be improved in the plugin so it can go back to the non-
unawaited
version? This feels a little bit like the plugin is relying in race conditions all the time to work!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.
Whether the overall design of these enclosing functions not every being
awaited
can be addressed without breaking changes to clients I'm not sure yet. I believe these could be fixed locally to await by changing the flow of each one to:_foo
tooldFoo
_foo
(currently done after the unawaited async)await
ed call usingoldFoo
instead of_foo
as the previous value argument.I considered doing that in this PR, or leaving a TODO in the code to do it later, but decided that since the only current use of these private methods is from a non-async function that can't await them anyway it wasn't clear that there was a real benefit to doing so. We could certainly revisit though, since I agree it feels a bit weird.