-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fix: MapObjectManager.Collection object order #972
Conversation
…s#846) Bumps play-services-base from 17.2.1 to 17.6.0. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.
@jeffdgr8 Thanks for working on this! A few comments in-line.
@@ -56,7 +56,7 @@ dependencies { | |||
implementation 'com.google.android.libraries.maps:maps:3.1.0-beta' | |||
implementation 'com.android.volley:volley:1.2.1' // TODO - Remove this after Maps SDK v3 beta includes Volley versions on Maven Central | |||
implementation 'com.google.android.gms:play-services-basement:17.6.0' | |||
implementation 'com.google.android.gms:play-services-base:17.2.1' | |||
implementation 'com.google.android.gms:play-services-base:17.6.0' |
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.
Is this dependency change needed? If not, could you please revert for this PR, and if so, could you please explain why?
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.
This came over from this commit on the old master branch. It's the only of the 5 commits ahead of the new main branch master had that haven't since been updated to newer dependencies already on main. Looks like the chore bot is now doing those dependency updates on main. Might be able to delete the master branch now entirely.
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.
Huh, strange - thanks for pointing that out. Not sure why dependabot didn't bump that in main
.
@arriolac thoughts on removing master
branch entirely? It might reduce confusion for folks that have it cloned locally on their machine who haven't realized that the main branch switched to main
.
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.
++ to deleting master
completely to avoid any confusion. Will go ahead and do that.
@@ -24,7 +24,7 @@ | |||
|
|||
import java.util.Collections; | |||
import java.util.HashMap; | |||
import java.util.HashSet; | |||
import java.util.LinkedHashSet; |
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.
Should mNamedCollections
and mAllObjects
on lines 43/44 be changed to LinkedHashMap
s for predictable order as well?
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 just confirmed that neither of those collections are able to be iterated over, so consistent ordering should never be an issue there. Only get()
, put()
, and remove()
operations are performed on them internally and there's no API that returns these collections to an external caller.
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.
Ok, thanks, that looks right.
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.
Thanks for the contribution @jeffdgr8!
🎉 This PR is included in version 2.2.6 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
BREAKING CHANGE
footer so when this change is integrated a major version update is triggered. See: https://www.conventionalcommits.org/en/v1.0.0/Fixes #772 🦕