Test merge#6
Open
ksincennes wants to merge 248 commits into
Open
Conversation
# Conflicts: # android/src/main/java/com/airbnb/android/react/maps/AirMapModule.java
# Conflicts: # components/MapView.js # ios/AirMaps/AIRMapManager.m
…eact-native-maps#801) * Add support for polygon holes for Apple Maps and Google Maps on iOS * Add PropTypes for polygon holes * Add support for polygon holes in Polygon Creator example
Help fixing issue blank map on android
…eact-native-maps#840) * Fixes react-native-maps#470 for iOS and Apple Maps This will add support for `legalLabelInsets` prop on iOS with Apple Maps. Code is adapted from RN core. * Pluralize updateLegalLabelInset(s) for consistency * Removed arrow notation * Added legalLabelInsets example
* Update mapview.md Updated documentation to match the example here (https://github.com/airbnb/react-native-maps/blob/master/example/examples/FitToCoordinates.js) * Changed name from 'arguments' to 'options'
) * Allow legalLabelInsets to be changed and animated Updated example to include a button to animate the legal label. * Docs for legalLabelInsets prop While structurally identical to EdgePadding, they serve completely different purposes. Default left empty since it's an OS default (around {left: 10, bottom: 10}) * Spacing / linting
…esnapshot-android Added support for taking snapshots on Android
…ve-maps#904) - Updated descriptions of getting and using Android API Keys. It works differently than when this was originally written. - Added fix for DexException - Added "import" in map component code
…ps#910) * Updating the android installation docs This adds a method to fix the mismatch between the play-services in case the user wants to use a different version * Fix syntax for some versions of gradle Fixed some syntax as suggested by @Froelund as the previous one doesn't work on some versions of gradle.
* fixes Option 2 building - afaik `GMSMapStyle` is not present in 2.0.x * Update installation.md * Update installation.md
…RN 0.40 React Native 0.40 (coming soon) changes the way its iOS headers should be imported. The headers are now under a directory called "React" that is in the compiler's include path, hence the new import style. On the JS side, RN 0.40 now peer-depends on React 15.4.x which moved SyntheticEvent from `react/lib` to deep inside `react-native`, so update that import as well. Test Plan: Follow the setup instructions (https://github.com/airbnb/react-native-maps/blob/master/docs/examples-setup.md) and run the explorer app (notably verify that it compiles).
Tested it with Google Maps support.
[RN 0.40] Update iOS header imports and JS SyntheticEvent import for RN 0.40
…ments-Fix Fixed issue react-native-maps#751.
…ve-maps#1734) If the files are not copied during dragging the folder, your iOS project will fail to build
Ignore this if the changelog is generated from commits or something.
…#1710) `OnCameraChangeListener` is deprecated and should no longer be used. This PR adds support for new more powerful APIs and removes the old hacky region detection code. This fixes various issues and paves the way for distinguishing between gestures and manual/programatic animations the same time. https://developers.google.com/android/reference/com/google/android/gms/maps/GoogleMap.OnCameraChangeListener
…ct-native-maps#1705) Fixes issue react-native-maps#1031, enabling use of custom marker images and views in Google Maps on iOS and android. As detailed in the Google Maps Marker documentation (kudos to @hughvidos), map markers track view changes by default. This has meant however that custom marker images or views on iOS and android, when using Google Maps, cause high continuous CPU load. The recommended use of tracksViewChanges is to enable when the marker is being rendered or animated, then to disable it. An example of use of tracksViewChanges would be to set it to false once onMapReady has fired. This can be accomplished by toggling a state property (e.g. `initialized`), and passing it to the child map markers in their `tracksViewChanges` prop. Markers would then render correctly on map load; CPU use falls off once the tracking ceases.
* Added new iOS `mutedStandard` map-type * Update MapView.js
…pe for native prop 'AIRMapMarker.testId' of native type 'String' (react-native-maps#1792) * Be less specific about react-native version for android * Relax play services dependencies as well * Fixes issue with ReactNative 0.42.3 * Update MapMarker.js * Make all components use ViewPropTypes || View.propTypes
* Add mapPadding property * Fix trailing whitespace in MapView comments
* Add setMapBoundaries method iOS * Add setMapBoundaries method android * Add setMapBoundaries method to MapView component * Update MapView docs * Add note to setMapBoundaries method
You need to enable Google maps API in the google developer console for android/ios
There was a typo in the new iOS mapType `mutedStandard`. It should have been `mutedStandard` instead of `standardMuted`
…-native (react-native-maps#1839) [AirGoogleMapManager] Use RCTDirectEventBlock for onMarkerPress
this is to resolve compile error: Property 'cameraTargetBounds' not found on object of type 'AIRGoogleMap *'
adding bracket
fix missing dependency
add missing line
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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.
No description provided.