-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD for payment 2024-03-13] [$500] Workspace – Unable to save edited WS name using Enter key in newly created WS. #36923
Comments
Triggered auto assignment to @kadiealexander ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Workspace – Unable to save edited WS name using Enter key in newly created WS. What is the root cause of that problem?We don't pass
What changes do you think we should make in order to solve the problem?Pass Result |
Can't reproduce on v1.4.43-5 2024-02-21_13-54-48.mp4 |
Able to reproduce. Screen.Recording.2024-02-20.at.8.53.51.PM.mov |
Still unable to repro: 2024-02-21_15-39-18.mp4 |
Ah wait, I clicked the wrong "create a workspace" button. Was able to repro this. |
Job added to Upwork: https://www.upwork.com/jobs/~0109e93e51a9b4c9ed |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.The enter key to save the workspace name doesn't work after creating a new workspace from the switcher page. What is the root cause of that problem?Summary: The ENTER key is captured by another page. When we press the new workspace from the switcher page, we will be navigated to the newly created workspace page (profile). App/src/pages/WorkspaceSwitcherPage.tsx Lines 220 to 222 in 6989089
We never pop the switcher page out from the nav stack, so it still exists on the stack. The workspace switcher page uses App/src/components/OptionsSelector/BaseOptionsSelector.js Lines 124 to 131 in 6989089
But we have another condition to subscribe it back. App/src/components/OptionsSelector/BaseOptionsSelector.js Lines 116 to 122 in 6989089
App/src/components/OptionsSelector/BaseOptionsSelector.js Lines 269 to 280 in 6989089
When we press the new workspace button, This only happens when you have at least 1 workspace because if you have none, the options selector won't be rendered. App/src/pages/WorkspaceSwitcherPage.tsx Lines 237 to 238 in 6989089
What changes do you think we should make in order to solve the problem?We have an unsubs code for the App/src/components/OptionsSelector/BaseOptionsSelector.js Lines 290 to 296 in 6989089
Unsubs them when the screen is out of focus. App/src/components/OptionsSelector/BaseOptionsSelector.js Lines 124 to 131 in 6989089
What alternative solutions did you explore? (Optional)Only do the subscription if App/src/components/OptionsSelector/BaseOptionsSelector.js Lines 116 to 122 in 6989089
OR Pop the switcher page when creating a new workspace. App/src/pages/WorkspaceSwitcherPage.tsx Lines 220 to 222 in 6989089
I think we should do this regardless of the solution selected. |
@bernhardoj's proposal (Main solution) looks good to me. works well. |
Triggered auto assignment to @francoisl, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
📣 @getusha 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
PR is ready cc: @getusha |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.47-10 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-03-13. 🎊 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:
|
@getusha don't forget the checklist! |
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 👎 |
Payouts due:
Upwork job is here. |
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: 1.4.43-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: https://expensify.testrail.io/index.php?/tests/view/4327666
Email or phone of affected tester (no customers): applausetester+jp_e_category@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
Edited WS name is saved
Actual Result:
Nothing happens
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6385818_1708442372353.Unable_to_save_edited_WS_name_using_Enter_key.1.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: