Closed lanitochka17 closed 2 months ago
Triggered auto assignment to @Beamanator (DeployBlockerCash
), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.
:wave: Friendly reminder that deploy blockers are time-sensitive β± issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Job added to Upwork: https://www.upwork.com/jobs/~021832081817508149579
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (External
)
Report fields - No checkbox next to list value on web layout
Offending PR https://github.com/Expensify/App/pull/46788
In the above PR, we changed to use shouldUseNarrowLayout
in ReportFieldsListValuesPage
component, which always returns true because the component is displayed in RHP.
Therefore, the list value is displayed as in small-screen devices, although it's on a large-screen device https://github.com/Expensify/App/blob/cadd5a85f0d9508bcb1063480f1a76259735487d/src/pages/workspace/reportFields/ReportFieldsListValuesPage.tsx#L70
I think we should revert to using isSmallScreen
in ReportFieldsListValuesPage
, the same as previously. Because, I think we intended to display the list in either small-screen or large-screen devices here, not related to the narrow layout.
Result:
There is no checkbox next to each list value The checkbox only appears when long clicking on the list value, which brings up the stretched pop-up
Currently, in here the value of the shouldUseNarrowLayout
variable is true
even though we are on a large screen because it is being used in the modal.
It causes the value of the canSelectMultiple
variable to be false
here, leading to a UI issue.
We should use isSmallScreenWidth for this case like we did here and here
// We need to use isSmallScreenWidth instead of shouldUseNarrowLayout to use the correct modal type
const {isSmallScreenWidth} = useResponsiveLayout();
https://github.com/user-attachments/assets/f535d00d-ef99-4e93-b15a-0d5a0cd10236
Will be fixed in https://github.com/Expensify/App/pull/48723
π£ @ahmedGaber93 π An offer has been automatically sent to your Upwork account for the Reviewer role π Thanks for contributing to the Expensify app!
π£ @rayane-djouah π An offer has been automatically sent to your Upwork account for the Contributor role π Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review π§βπ» Keep in mind: Code of Conduct | Contributing π
@rayane-djouah assigning you since you're the author of https://github.com/Expensify/App/pull/46788 which caused this blocker & you're working on the fix in https://github.com/Expensify/App/pull/48723
Hi, Is this task already completed? I recently saw a job post regarding this task on upwork but from here, it seems the matter is already resolved.
Here, is the job post link: https://www.upwork.com/jobs/~021832081817508149579
π£ @haris-aqeel! π£ Hey, it seems we donβt have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork. Please follow these steps:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Hi @haris-aqeel - yes sorry this job is already assigned out and being worked on in https://github.com/Expensify/App/pull/48723
Most available jobs in our Github repository will have the Help Wanted
label assigned right now
Contributor details Your Expensify account email: harisaqeel.2001@gmail.com Upwork Profile Link: https://www.upwork.com/freelancers/harisaqeel34
β Contributor details stored successfully. Thank you for contributing to Expensify!
β οΈ Looks like this issue was linked to a Deploy Blocker here
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
The fix was CPed to staging
closing since fix was CP'd and was fixed as regression so no payment needed
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: 9.0.30-10 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers): applausetester+kh010901@applause.expensifail.com Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
There will be checkbox next to each list value (production behavior)
Actual Result:
There is no checkbox next to each list value The checkbox only appears when long clicking on the list value, which brings up the stretched pop-up
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/user-attachments/assets/698e4789-94e8-4b7f-b983-744942d04152
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ahmedGaber93