-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$500] [Distance] - Automatic Saving of Start or End Point and Redirection to Distance Page Renders Save Button Useless #27108
Comments
ProposalPlease re-state the problem that we are trying to solve in this issue.[Distance]Automatic Saving of Start or End Point and Redirection to Distance Page Renders Save Button Useless What is the root cause of that problem?When selecting the address, the App will redirect to Distance request Page by this logic App/src/pages/iou/WaypointEditor.js Line 157 in 57b7606
What changes do you think we should make in order to solve the problem?We should hide the save button in the WaypointEditor Page App/src/pages/iou/WaypointEditor.js Line 193 in 57b7606
Here, we add
and remove redundant props like submitButtonText, onSubmit... What alternative solutions did you explore? (Optional)when selecting option, we don't navigate back by removing this line App/src/pages/iou/WaypointEditor.js Line 157 in 57b7606
|
Triggered auto assignment to @abekkala ( |
Job added to Upwork: https://www.upwork.com/jobs/~0110ac5e7e0555b43d |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @greg-schroeder ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @robertKozik ( |
I think it will be fixed #27021 |
Wanted to contribute on this one... but I guess it's taken :( |
📣 @iamsid47! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
ProposalPlease re-state the problem that we are trying to solve in this issue.[Distance] - Automatic Saving of Start or End Point and Redirection to Distance Page Renders Save Button Useless What is the root cause of that problem?/App/src/pages/iou/WaypointEditor.js What changes do you think we should make in order to solve the problem?To address the problem, we should consider removing this line. Instead, we should implement the redirection behavior exclusively when the save button is clicked. This approach maintains consistency, especially since the save button is currently designed to function offline. What alternative solutions did you explore? (Optional)N/A Screencast.from.10-09-23.19.36.49.webm |
📣 @MbuguaGeorge! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Not the same bug ,it is different |
@robertKozik can you confirm if the fix for this will be fixed via #27021 or not |
@abekkala I'm also a C+ on #27021. Chosen proposal does not contain removing the save button, as it should only address saving waypoints in offline mode. That's why I think we should fix this issue individually, but as this would contain only removing the submit button or removing redirect function, we can consider reducing the bounty due to simplicity of this issue |
Thank you all for your proposals! 🙇🏼 Moreover as in issue #27021 we will probably remove the possibility of typing random waypoint in offline mode, the save button will become obsolete in every scenario as choosing waypoint from the list will trigger the redirect, so we should go with your main proposed solution - removing the submit button Selected Proposal: Proposal 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @tgolen, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
📣 @DylanDylann 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
📣 @tewodrosGirmaA 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app! |
@robertKozik The PR is ready for review |
Hello! I'm following up on issue #27021. It seems that saving from the autocomplete dropdown should be an option for offline flows. Since I don't have access to the Slack conversation mentioned in this comment, could we please double-check whether this behavior is indeed a bug or if it's intended? |
@thienlnam I see that you implement offline flow in distance request. So could you help to check this comment ? |
@robertKozik I think everything is fine here. This issue is only about removing the save button because it functionally has no purpose since everything is automatically saved when you select a waypoint. #27021 Is about being able to select an invalid waypoint when you are offline. Maybe I'm not quite understanding your question, but I don't see how these are directly related.
Could you please clarify what "this behavior" is that you are asking about? I'm not sure what it's referring to. |
Yeah, it's possible to enter in a waypoint offline - so I don't think this is a bug and we can close. We could remove the save button while you're online? But I don't really see the need to update that flow |
@tgolen @robertKozik please help to take a look at this comment when you are free? And then we can move forward with this issue |
It's just so weird to leave a button there when it has zero functionality. I'd remove it. |
@tgolen when offline, there are no suggestion address for user. So user only can enter address manually and click save button |
It is not required for the online flow, but is required for the offline flow. Are you suggesting removing it for just the online flow? |
OK, I understand now. If it's needed for one of the flows, let's leave it
there for both flows and we can just close this.
…On Mon, Sep 25, 2023 at 10:06 AM Jack Nam ***@***.***> wrote:
It's just so weird to leave a button there when it has zero functionality.
I'd remove it.
It is not required for the online flow, but is required for the offline
flow. Are you suggesting removing it for just the online flow?
—
Reply to this email directly, view it on GitHub
<#27108 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJMAB7NVFZ4LU4XCNO6HW3X4DRIZANCNFSM6AAAAAA4SGZOIQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
hello @abekkala , i get an offer but payment is not settled |
@abekkala Are we eligible for compensation for our effort? Contributors are already assigned and started on the PR. It's just due to the expectation changes and the solution becomes outdated. Some other similar cases where compensation is made are below: |
based on this #18664 (comment) Sending payment offers to
|
@tewodrosGirmaA [$50] - payment sent and contract ended @DylanDylann [$500] - payment sent and contract ended |
Thank you @abekkala 😊 |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
The Save button should either work correctly or be removed. When a start or end point is selected, the location should be chosen but not saved until the user clicks Save. The app should remain on the current page until the user decides to save and then redirect to the Distance page.
Actual Result:
Selecting a start or end point automatically saves the location and redirects to the Distance page, making the Save button unnecessary.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.66.3
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
screen-capture.-.2023-09-05T045157.755.webm
Recording.4364.mp4
Expensify/Expensify Issue URL:
Issue reported by: @tewodrosGirmaA
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693914355944309
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: