-
Notifications
You must be signed in to change notification settings - Fork 942
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
Reorganize maps configuration #900
Conversation
7b6c989
to
62053d1
Compare
// obfuscated coordinates are withing a circle that has the same | ||
// radius as the offset. | ||
coordinateOffset: 500, | ||
const maps = { |
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.
We could call this map
as the application is using one map at a time. But I guess maps
makes sense too.
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.
Well, you sort of configure all the maps in the app. And nothing prevents using two or more maps at a time. But mainly maps
is a bit more greppable than map
.
62053d1
to
8926411
Compare
Merging this so that we can base the actual Mapbox changes on top of this. |
BREAKING CHANGE
This PR reorganises the maps configuration to work with both Google Maps and Mapbox. The structure of the configuration is different and paves the way for the bigger change of making Mapbox as the default map provider.
NOTE: Can we merge this already? This will create conflicts if people have edited the related settings in
config.js
. Although multiple smaller breaking changes is better than one huge one when the whole Mapbox feature lands.Update docs(another PR)