-
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
Add Guides call request flow to workspace card configuration screen #4637
Conversation
Putting on hold for this https://github.com/Expensify/Expensify/issues/173720#issuecomment-898323941 |
@@ -32,6 +33,11 @@ const propTypes = { | |||
/** Whether we should show a download button */ | |||
shouldShowDownloadButton: PropTypes.bool, | |||
|
|||
/** Whether weshould show a inbox call 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.
/** Whether weshould show a inbox call button */ | |
/** Whether we should show a inbox call 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.
Lookin good! Some minor changes/concerns
Off hold @chiragsalian @jasperhuangg |
@@ -77,6 +86,11 @@ const HeaderWithCloseButton = props => ( | |||
) | |||
} | |||
|
|||
{ | |||
props.shouldShowInboxCallButton && <InboxCallButton taskID={props.inboxCallTaskID} /> | |||
|
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.
remove the unnecessary line break
@@ -21,11 +21,13 @@ import ROUTES from '../ROUTES'; | |||
const propTypes = { | |||
...withLocalizePropTypes, | |||
...windowDimensionsPropTypes, | |||
isConcierge: PropTypes.bool, | |||
openInboxCall: PropTypes.bool, |
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.
openInboxCall
feels like an odd name for a boolean. I feel like this should start with is
or should
, maybe something like shouldOpenInboxCall
or something. Either way, looking at the logic and now understanding it i felt like isConciergeChat
is more obvious of a variable to understand whats going on i.e., if not concierge chat, open video menu, else if concierge chat open inbox call to schedule a setup call.
If you'd like to keep inboxCall then maybe add some comments explaining what happens if this variable is true or false.
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.
Ah yes, before all the design changes, the new button also used this flow, so the variable name was changed. Since the design changes mean they are two different flows, I will change this back! Good catch
src/pages/home/HeaderView.js
Outdated
@@ -158,7 +158,7 @@ const HeaderView = (props) => { | |||
{props.report.hasOutstandingIOU && ( | |||
<IOUBadge iouReportID={props.report.iouReportID} /> | |||
)} | |||
<VideoChatButtonAndMenu isConcierge={isConcierge} /> | |||
<VideoChatButtonAndMenu openInboxCall={isConcierge} taskID="ExpensifyCashConciergeDM" /> |
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.
Thoughts on making the 2nd param consistent and more verbose i.e., instead of taskID
calling it inboxCallTaskID
.
Two reasons why I suggest this,
taskID
forVideoChatButtonAndMenu
doesn't mean much imo so someone needs to look at the code to know what it is.- Renaming to
inboxCallTaskID
would keep it consistent to the variable here.
Updated! |
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.
Small question. Rest LGTM
if (this.props.openInboxCall) { | ||
Navigation.navigate(ROUTES.getRequestCallRoute(this.props.taskID)); | ||
if (this.props.isConcierge) { | ||
Navigation.navigate(ROUTES.getRequestCallRoute('NewExpensifyConciergeDM')); |
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.
umm whats NewExpensifyConciergeDM
? i don't see this on web-e master.
Don't you mean ExpensifyCashConciergeDM
? Or is there a PR i'm unaware of that's updating this text?
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.
The taskID was updated in this PR #4408
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.
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.
No I don't think you are missing something, I think that was missed in the other updates PR. I'll spin up a separate PR for that.
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.
PR: https://github.com/Expensify/Web-Expensify/pull/31749
Follow up issue to remove the old task ID from web: https://github.com/Expensify/Expensify/issues/174159
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.
So does this PR now go on HOLD till the web-E code is on production or not really?
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.
I think that since this is a n6 issue, we should avoid HOLDing this. We can CP the other PR to help with backwards compatability
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.
LGTM
Lookin good! Feel free to merge if the Web-E stuff with taskID is all good. |
The task ID stuff has been merged and cp'd! Merging this! Thanks for the reviews yall! |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
This PR is on staging. Can you try the flow again, but have your JS console open so that I can see the error (if there is any) |
It worked! @alex-mechler |
#4866 this issue was found while executing this PR |
🚀 Deployed to production by @roryabraham in version: 1.0.88-2 🚀
|
cc @jasperhuangg
Details
This PR does two things
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/173720#issuecomment-897795837
Tests
Regression Tests
Expensiworks/InboxCallUser
job with the taskIDExpensifyCashConciergeDM
in your jobs tableFeature Tests
New Workspace
buttonCompany Cards
buttonExpensiworks/InboxCallUser
job with the taskIDWorkspaceCompanyCards
in your jobs tableQA Steps
New Workspace
buttonCompany Cards
buttonRepeat for each platform
Tested On
Screenshots
Web
Also tested the translation on web
![image](https://user-images.githubusercontent.com/22447860/129934314-6a89ee13-23fd-4ccd-8261-14a68d4710ec.png)
Mobile Web
Desktop
iOS
Android