Conversation
Update README.md small change which caused confusion
## [1.18.1](react-native-maps/react-native-maps@v1.18.0...v1.18.1) (2024-10-12) ### Bug Fixes * documentation on README.md ([react-native-maps#5174](react-native-maps#5174)) ([b853f3a](react-native-maps@b853f3a))
…-maps#5167) * fix(ios): do not store the original map
….0.0 (react-native-maps#5183) * fix(map): prevent overrideGestureRecognizers from being called multiple times per view * chore(map): update GoogleMaps SDK to v8.4 * chore(map): update Google-Maps-iOS-Utils to v5.0.0 * docs(map): update minimum iOS version to 14 for GoogleMaps projects
…t-native-maps#5184) * feat(iOS): add support for loadingBackgroundColor for GoogleMaps on iOS * chore(iOS): remove call for deprecated setMetalRenderer (already the default) * chore(iOS): enable LoadingMap example for GoogleMaps on iOS
…eact-native-maps#5185) fix: correctly check for iOS OS version before using cameraZoomRange
## [1.18.2](react-native-maps/react-native-maps@v1.18.1...v1.18.2) (2024-10-14) ### Bug Fixes * correctly check for iOS OS version before using cameraZoomRange ([react-native-maps#5185](react-native-maps#5185)) ([4efd881](react-native-maps@4efd881))
… consistency with Android (react-native-maps#5196) fix(iOS): refactor onPress(Marker) to return nativeEvent.position instead of nativeEvent.point for consistency with Android and documentation react-native-maps#4996 followup
## [1.18.3](react-native-maps/react-native-maps@v1.18.2...v1.18.3) (2024-11-09) ### Bug Fixes * **iOS:** Refactor onPress(Marker) to return nativeEvent.position for consistency with Android ([react-native-maps#5196](react-native-maps#5196)) ([956783f](react-native-maps@956783f)), closes [react-native-maps#4996](react-native-maps#4996)
…ative-maps#5150, react-native-maps#5152, react-native-maps#5153, react-native-maps#5154) (react-native-maps#5151) * fix(Android): reapply camera after padding is updated * fix(Android): defer setPadding until the map is laid out. * fix(Android): call moveToCamera() with initialCamera property * fix(Android): keep edgePadding when updating mapPadding property * fix(Android): remove 50px padding specified by fixToXXX() Fixes react-native-maps#5150 Fixes react-native-maps#5152 Fixes react-native-maps#5153 Fixes react-native-maps#5154
## [1.18.4](react-native-maps/react-native-maps@v1.18.3...v1.18.4) (2024-11-09) ### Bug Fixes * **Android:** fix multiple padding related issues on Android ([react-native-maps#5150](react-native-maps#5150), [react-native-maps#5152](react-native-maps#5152), [react-native-maps#5153](react-native-maps#5153), [react-native-maps#5154](react-native-maps#5154)) ([react-native-maps#5151](react-native-maps#5151)) ([0009170](react-native-maps@0009170))
… Map (react-native-maps#5162) (react-native-maps#5163) * fix(ios): setCamera calls before layoutSubviews are ignored on Google Map (react-native-maps#5162) Fixes react-native-maps#5162
# [1.19.0](react-native-maps/react-native-maps@v1.18.4...v1.19.0) (2024-11-09) ### Features * add onRegionChangeStart event to MapView ([react-native-maps#5144](react-native-maps#5144)) ([eeb56f9](react-native-maps@eeb56f9))
fix: Remove unstable_reactLegacyComponentNames New architecture is now enabled by default. chore: Update react-native to 0.76.1 Updated development dependencies for semantic-release
## [1.19.1](react-native-maps/react-native-maps@v1.19.0...v1.19.1) (2024-11-10) ### Bug Fixes * Remove unstable_reactLegacyComponentNames ([react-native-maps#5209](react-native-maps#5209)) ([33112be](react-native-maps@33112be))
…5210) - helps improve android click handling Co-authored-by: salah ghanim <salah@getaway.pro>
# [1.20.0](react-native-maps/react-native-maps@v1.19.1...v1.20.0) (2024-11-10) ### Features * **android:** add support for disabling PoIClick ([react-native-maps#5210](react-native-maps#5210)) ([d92e283](react-native-maps@d92e283))
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
10 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.
Rebasing with original library