-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Map panning fix (2) #26500
Map panning fix (2) #26500
Conversation
* Fix Map Panning behavior * Add screen focus state props to MapView Added new props to avoid introducing unnecessary dependencies ('@react-navigation/native') to the 'react-native-x-maps' library. * feat: Move code from react-native-x-maps to the App * fix: rename mapbox consts * fix: Fix app crashing on waypoint delete * Remove unnecessary re exports * Fix react duplicate keys Expensify#35 * Fix Not Found Page appearing issue and add comment * Fix panning issue * fix: add PropTypes import which is mised during conflict resolution
@allroundexperts Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
Reviewer Checklist
Screenshots/VideosWebScreen.Recording.2023-09-01.at.2.30.23.AM.movMobile Web - ChromeScreen.Recording.2023-09-01.at.2.48.03.AM.movMobile Web - SafariScreen.Recording.2023-09-01.at.2.37.04.AM.movDesktopScreen.Recording.2023-09-01.at.3.07.59.AM.moviOSScreen.Recording.2023-09-01.at.2.33.23.AM.movAndroidScreen.Recording.2023-09-01.at.3.03.36.AM.mov |
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.
Coming from #25977, this PR was already approved.
We did not find an internal engineer to review this PR, trying to assign a random engineer to #25732 as well as to this PR... Please reach out for help on Slack if no one gets assigned! |
@hayata-suenaga Your review needed here! |
@gegham-khachatryan lint is failing |
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.
LGMT minus the lint errors
Fixing lint errors |
Inside |
299d030
@neil-marcellini Lint errors fixed @allroundexperts Also updated ConfirmedRoute.js component. |
@hayata-suenaga #26500 |
running CI tests again... |
Testing this now... |
@allroundexperts I know this is the copy of the original PR but can you just go through the basic flow just to make sure it still works? |
On it! |
Working good for me! |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by https://github.com/neil-marcellini in version: 1.3.62-0 🚀
|
🚀 Deployed to production by https://github.com/mountiny in version: 1.3.62-4 🚀
|
@@ -161,7 +163,7 @@ function WaypointEditor({transactionID, route: {params: {iouType = '', waypointI | |||
onEntryTransitionEnd={() => textInput.current && textInput.current.focus()} | |||
shouldEnableMaxHeight | |||
> | |||
<FullPageNotFoundView shouldShow={Number.isNaN(parsedWaypointIndex) || parsedWaypointIndex < 0 || parsedWaypointIndex > waypointCount - 1}> |
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.
@gegham-khachatryan Can you please help explain why do we need to use && isFocused
here? Thanks
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.
@ahmedGaber93 There was an issue where when deleting a waypoint, transactions were updated before the page close animation occurred, and the Not Found screen became visible for a few milliseconds during the animation.
@@ -0,0 +1,13 @@ | |||
function getBounds(waypoints: Array<[number, number]>): {southWest: [number, number]; northEast: [number, number]} { | |||
const lngs = waypoints.map((waypoint) => waypoint[0]); | |||
const lats = waypoints.map((waypoint) => waypoint[1]); |
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.
Hi ✋ Coming from #27175
To enhance the bounds, we also should be considering the direction coordinates so it can be zoomed out from the furthest distance.
Details
Fixed Issues
$ #25732
PROPOSAL: #25732 (comment)
Tests
Offline tests
QA Steps
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)myBool && <MyComponent />
.src/languages/*
files and using the translation methodWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)ScrollView
component to make it scrollable when more elements are added to the page.main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps.Screenshots/Videos
Web
Web.-.Screen.Recording.2023-08-26.at.09.52.07.mov
Mobile Web - Chrome
Web.Mobile.Chrome.-.iPhone.14.Pro.MP4
Mobile Web - Safari
Web.Mobile.Safari.-.Simulator.Screen.Recording.-.iPhone.SE.3rd.generation.-.2023-08-26.at.09.39.49.mp4
Desktop
Screen.Recording.2023-08-26.at.10.28.32.mov
iOS
Simulator.Screen.Recording.-.iPhone.SE.3rd.generation.-.2023-08-26.at.00.58.04.mp4
Android
Screen.Recording.2023-08-26.at.16.34.28.mov