You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
LHN can be scrolled horizontally while closed. #3781
👋 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:
Identify the pull request that introduced this issue and revert it.
yeah as overflow is in Y-axis so overflowX will not have any effect. But I am yet to test the issue but before I need to reproduce it. Will share an update today on that.
Hey, @MitchExpensify@roryabraham. I reproduced #3768 and tested my solution over it and guess what I was correct. we have to prevent overflow on the Drawer screen to fix both of the issues.
@MitchExpensify Since you're conveniently managing both this issue and #3768, let's hire @parasharrajat for the one Upwork Job, then assuming his PR fixes both issues (like it looks like it will), let's pay him:
For that upwork job
A bonus for this issue (since AFAICT there's no Upwork job here yet)
Plus the additional bounty for opening for this issue and also providing the solution.
Oops, sorry I got confused here @stephanieelliott and thought @MitchExpensify was managing this issue. If the above sounds like a good plan I would suggest just reassigning this to @MitchExpensify to manage after the PR is merged.
Since there is a proposal here, we actually need to pay these jobs out separately to keep this clean in terms of Upwork ToS. So rather than paying out via a bonus, let's post this a separate job and hire Rajat to it directly if the PR solves both issues.
Tossing back to @MitchExpensify to manage, but feel free to reassign to me if the plan changes!
Activity
MelvinBot commentedon Jun 28, 2021
Triggered auto assignment to @stephanieelliott (
AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.parasharrajat commentedon Jun 28, 2021
Proposal
overflow-x:hiddento fix this issue.I think this will fix #3768 as well.
OSBotify commentedon Jun 29, 2021
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:MelvinBot commentedon Jun 29, 2021
Triggered auto assignment to @marcaaron (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.roryabraham commentedon Jun 29, 2021
Oh, jk this doesn't need to be a deploy blocker because it exists on production too.
5 remaining items
parasharrajat commentedon Jun 29, 2021
yeah as overflow is in Y-axis so overflowX will not have any effect. But I am yet to test the issue but before I need to reproduce it. Will share an update today on that.
parasharrajat commentedon Jul 1, 2021
Hey, @MitchExpensify @roryabraham. I reproduced #3768 and tested my solution over it and guess what I was correct. we have to prevent overflow on the Drawer screen to fix both of the issues.
To fix both issues:
cardStyle: {overflow: hidden}option to the Drawer route here https://github.com/Expensify/Expensify.cash/blob/c5707430dff9ecfb631012bb0ba25357c7f367e5/src/libs/Navigation/AppNavigator/AuthScreens.js#L236.So this route will change to this code.
fix-scroll.mp4
parasharrajat commentedon Jul 1, 2021
Waiting for the next instructions. Let's get this fix pushed which crosses off two issues from the board. Thanks.
roryabraham commentedon Jul 1, 2021
@MitchExpensify Since you're conveniently managing both this issue and #3768, let's hire @parasharrajat for the one Upwork Job, then assuming his PR fixes both issues (like it looks like it will), let's pay him:
roryabraham commentedon Jul 1, 2021
Oops, sorry I got confused here @stephanieelliott and thought @MitchExpensify was managing this issue. If the above sounds like a good plan I would suggest just reassigning this to @MitchExpensify to manage after the PR is merged.
stephanieelliott commentedon Jul 1, 2021
Since there is a proposal here, we actually need to pay these jobs out separately to keep this clean in terms of Upwork ToS. So rather than paying out via a bonus, let's post this a separate job and hire Rajat to it directly if the PR solves both issues.
Tossing back to @MitchExpensify to manage, but feel free to reassign to me if the plan changes!
MitchExpensify commentedon Jul 1, 2021
Sounds good! So I will reopen that Upwork job (done!), accept Rajat's proposal, and pay (with bonus) 7 days after merge assuming all goes smoothly. .
MelvinBot commentedon Jul 1, 2021
Triggered auto assignment to @Beamanator (
Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.parasharrajat commentedon Jul 1, 2021
PR is up #3856 already. It's a quick one and can be merged. Thanks.
MitchExpensify commentedon Jul 19, 2021
Sorry for the delay on bonus and bounty payment @parasharrajat while I wass ooo last week. That has now been made in Upwork!