-
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
[PAID] [$250] Web - Settings is opened on the left with a conversation opened on the right #49337
Comments
Triggered auto assignment to @strepanier03 ( |
@strepanier03 FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - Settings is opened on the left with a conversation opened on the right What is the root cause of that problem?Interaction manager is used to navigate back and due to this user can click multiple times until the navigation happes. App/src/pages/settings/Profile/CustomStatus/StatusPage.tsx Lines 113 to 115 in 2190f62
What changes do you think we should make in order to solve the problem?We should call What alternative solutions did you explore? (Optional)We can return early from Result |
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - Settings is opened on the left with a conversation opened on the right What is the root cause of that problem?When we click multiple times this code block executes multiple times App/src/pages/settings/Profile/CustomStatus/StatusPage.tsx Lines 113 to 115 in 2190f62
So it first takes us to - profile page, next time to report page What changes do you think we should make in order to solve the problem?We should wrap the submit callback in App/src/pages/settings/Profile/CustomStatus/StatusPage.tsx Lines 167 to 176 in 2190f62
const {singleExecution} = useSingleExecution() <FormProvider
formID={ONYXKEYS.FORMS.SETTINGS_STATUS_SET_FORM}
style={[styles.flexGrow1, styles.flex1]}
ref={formRef}
submitButtonText={translate('statusPage.save')}
submitButtonStyles={[styles.mh5, styles.flexGrow1]}
onSubmit={singleExecution(updateStatus)}
validate={validateForm}
enabledWhenOffline
> We can do similar changes for other callbacks as well. What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
App/src/pages/settings/Profile/CustomStatus/StatusPage.tsx Lines 113 to 115 in 2190f62
What changes do you think we should make in order to solve the problem?
App/src/pages/settings/Profile/CustomStatus/StatusPage.tsx Lines 129 to 131 in 2190f62
will be:
What alternative solutions did you explore? (Optional) |
Job added to Upwork: https://www.upwork.com/jobs/~021836565276008929567 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 ( |
Thanks all for the proposals. @BhuvaneshPatil add a proposal using @daledah add a proposal to remove @krishna232's alternative proposal looks good. It will return early if @krishna232's alternative proposal LGTM! 🎀 👀 🎀 C+ reviewed. |
Triggered auto assignment to @marcochavezf, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@ahmedGaber93 Thank you for feedback. But using |
@BhuvaneshPatil App/src/hooks/useSingleExecution/index.ts Lines 13 to 15 in 2190f62
App/src/hooks/useSingleExecution/index.native.ts Lines 17 to 20 in 2190f62
Also, I tested it, and it not works with me on web. 20240918233147910.mp4 |
Okay. Thanks for explanation. |
@ahmedGaber93 Thanks for your feedback. Let's see what @marcochavezf thinks about my thought above. |
@marcochavezf, @strepanier03, @ahmedGaber93 Eep! 4 days overdue now. Issues have feelings too... |
Not overdue, proposals is reviewed and waiting assignment. |
@marcochavezf Can you check my comment above? |
Hi guys, catching up from OOO thanks for the patience here. I will lean towards @ahmedGaber93's decision. I think the alternative solution proposed by @Krishna2323 is straightforward. The decision to remove Said that I will assign @Krishna2323, even though all perspectives and efforts are appreciated 🙇🏽 |
📣 @ahmedGaber93 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @Krishna2323 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@ahmedGaber93, PR ready for review ^ |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.44-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-10-11. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Few days away from payment so holding until then. |
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
Regression Test Proposal
Do we agree 👍 or 👎 |
I created the reg test GH, paid and closed both contracts, and I'm going to close this out now. Thanks, everyone! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: v9.0.36-1
Reproducible in staging?: Y
Reproducible in production?: Y
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
The modal to edit status is closed.
Actual Result:
Settings is opened on the left and a conversation is opened on the right.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6606512_1726571253654.bandicam_2024-09-17_13-43-32-991.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @strepanier03The text was updated successfully, but these errors were encountered: