-
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-09-04] [$250] Update UpdatePolicyConnectionConfiguration to be 1:1:1 - Part 2 #47520
Comments
Picking this up as C+ |
I'll take this one as contributor |
Job added to Upwork: https://www.upwork.com/jobs/~01f780930d7cefc51d |
Current assignee @ishpaul777 is eligible for the External assigner, not assigning anyone new. |
📣 @ishpaul777 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
I'll raise a PR soon |
Backend PR is merged, though not yet on staging, but should be soon! |
Spoke too soon, I guess - this is on staging now, so code away! |
yep perfect! double check that there aren't any other usages but that's it |
Little update, draft PR is here |
I think this is on prod? I'm going to grab a BZ to handle payment (and also help us figure that out haha) |
Triggered auto assignment to @joekaufmanexpensify ( |
@joekaufmanexpensify we're in the 7 day regression period for this one, but assigned you to help us figure out when this one went to prod and handle payment when payment is needed! |
Will take care of that now! |
Payment due here is:
|
All set to issue payment! |
@ishpaul777 $250 sent and contract ended! |
Upwork job closed. |
Closing as only thing left here is for @hungvu193 to request payment via NewDot! |
$250 approved for @hungvu193 |
Problem
Our UpdatePolicyConnectionConfiguration API command is not 1:1:1 - it is the same API call for all related user actions, when it should be split up for each connection (QBO, Xero, etc.) and configuration setting (
autoSyncVendor
,enableNewCategories
, etc.). At the end of this we should not call that function anywhere.This is polish for the Collect QBO project.
Solution
When we created the NetSuite commands, we followed the correct pattern, and so need to do so here too.
This requires backend and frontend work in tandem (to create the commands and then to use them), so we're looking for a contributor(s) to handle the frontend. You can see an example PR here - there is some extra prep work there that you can ignore, but adjusting all calls like this is what we're going for:
Here is a list of the commands handled in this issue:
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @The text was updated successfully, but these errors were encountered: