-
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
Refactor ReportActionItem
to use hooks
#18809
Conversation
@thesahindia @danieldoglas One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jasperhuangg sorry, another conflict |
@0xmiroslav good for another look! Fixed everything you mentioned above. |
@jasperhuangg lint failing |
Co-authored-by: Miroslav Stevanovic <[email protected]>
Co-authored-by: Miroslav Stevanovic <[email protected]>
@jasperhuangg I think the next time you fix conflicts here you should just ping in |
…pensify/App into jasper-refactorReportActionItemHooks1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thats some great hooks refactor here, thanks for getting through it @jasperhuangg!
Given the previous approvals and completed checklists, I am going to merge this to avoid further conflicts |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.17-0 🚀
|
🚀 Deployed to production by https://github.com/chiragsalian in version: 1.3.17-5 🚀
|
|
||
componentDidUpdate(prevProps) { | ||
if (prevProps.draftMessage || !this.props.draftMessage) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coming from #23886
Sometimes, the component will re-render when it is out of focus or the page reloaded, making the input focus unnecessary. To prevent this, we should keep the check against the previous draftMessage
, and only focus the input if the draftMessage
is changed.
memo( | ||
ReportActionItem, | ||
(prevProps, nextProps) => | ||
prevProps.displayAsGroup === nextProps.displayAsGroup && | ||
prevProps.draftMessage === nextProps.draftMessage && | ||
prevProps.isMostRecentIOUReportAction !== nextProps.isMostRecentIOUReportAction && | ||
prevProps.hasOutstandingIOU === nextProps.hasOutstandingIOU && | ||
prevProps.shouldDisplayNewMarker === nextProps.shouldDisplayNewMarker && | ||
!_.isEqual(prevProps.action, nextProps.action) && | ||
lodashGet(prevProps.report, 'statusNum') === lodashGet(nextProps.report, 'statusNum') && | ||
lodashGet(prevProps.report, 'stateNum') === lodashGet(nextProps.report, 'stateNum') && | ||
prevProps.translate === nextProps.translate, | ||
), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is missing the check for preferredSkinTone
prop changes. Coming from #42058
setIsContextMenuActive(true); | ||
|
||
const selection = SelectionScraper.getCurrentSelection(); | ||
ReportActionContextMenu.showContextMenu( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not handling focus removal from already focussed textinputs while showing context menu resulted in #44042
Details
Fixed Issues
$ #16264
Tests/QA Steps
[If testing locally perform these using the web proxy]
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)src/languages/*
files and using the translation methodWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)ScrollView
component to make it scrollable when more elements are added to the page.main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps.Screenshots/Videos
Web
web.mov
Mobile Web - Chrome
mweb-chrome.mov
Mobile Web - Safari
mweb-safari.mov
Desktop
desktop.mov
iOS
ios.mov
Android
android.mov