-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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-05-02] [Wave Collect][QBO] Create a HOC to call OpenAccountingPage
and then pass the report.connections
#39108
Comments
Triggered auto assignment to @strepanier03 ( |
changing priority back to daily as this has the high priority |
OpenAccountingPage
and then pass the report.connections
OpenAccountingPage
and then pass the report.connections
@hayata-suenaga - I am holding off labeling this Internal unless you give the go-ahead. I don't want to assign a C+ to do PR review if it's not needed. |
Job added to Upwork: https://www.upwork.com/jobs/~019f138fc4382cdf6a |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @eVoloshchak ( |
I decided to have a C+ review the PR just in case 😄 |
I realized that a C+ is already assigned to the PR. I'll assign them to this issue. |
Thank you @hayata-suenaga 🙌 |
Is the PR for this now on hold for #39652, @hayata-suenaga? If so, let's have that reflected in the title. |
OpenAccountingPage
and then pass the report.connections
OpenAccountingPage
and then pass the report.connections
OpenAccountingPage
and then pass the report.connections
OpenAccountingPage
and then pass the report.connections
@strepanier03, @mollfpr, @hayata-suenaga Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
PR is deployed to staging. |
The PR is actually still being worked on 🙇 |
@hayata-suenaga - sorry for the confusion, I meant the PR that this was on hold for is deployed to staging, not the PR for fixing for this issue 🤦♀️ |
ah haha sorry for my misunderstanding 🙇 🙈 |
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. |
OpenAccountingPage
and then pass the report.connections
OpenAccountingPage
and then pass the report.connections
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.65-5 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-05-02. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@hayata-suenaga - I was having a hard time figuring out the price here based on the PR that's linked. Is this a $500 payment or a $250 PR review payment? |
Payment Summary
BugZero Checklist (@strepanier03)
|
nvm, @hayata-suenaga - payment summary finally posted and I got my answer. |
Payment summary
@JmillsExpensify - Payment request incoming! |
$250 approved for @mollfpr |
Based on the discussion, implement a Higher-Order Component (HOC) that uses
useOnyx
to subscribe to policy data, then passes this data to the component it wraps. The HOC should inspect theconnections
field of the policy. If this field lacks a value in the policy data, the HOC should callOpenAccountingPage
.The HOC also should render the loading indicator or offline screen if necessary.
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: