-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: add map padding #373
base: main
Are you sure you want to change the base?
Conversation
@@ -188,6 +188,15 @@ export const useNavigationAuto = (): { | |||
moveCamera: (cameraPosition: CameraPosition) => { | |||
return NavAutoModule.moveCamera(cameraPosition); | |||
}, | |||
|
|||
setPadding: ( |
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.
Not sure about this order.
- iOS UIEdgeInsetsMake has currently implemented order: top, left, bottom, right.
- In Android API the order is: left, top, right, bottom.
- Using CSS (react users could be familiar with this) the order would be: top | right | bottom | left
Should we go with css order, or with Android (or keep the current iOS ordering).
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.
LGTM
And seems to work on both, Android and iOS.
On android the bottom padding does not move the re-center button like on iOS, but this is something that differs between Android and iOS SDKs.
Added one comment, waiting resolution from @ArturoSalazarB16 and @caio1985
Yeah, this got me confused for a moment. 😄 |
Fixes #292
This PR adds map padding support to both regular map view as well as Android auto/Carplay map views.