-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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-23][$250] Update UpdatePolicyConnectionConfiguration to be 1:1:1 - Part 1 #47443
Comments
Triggered auto assignment to @VictoriaExpensify ( |
Hey @dangrous - I notice that I got assigned to this with the bug label, but then you removed the bug label. So I'm not sure if I'm meant to be assigned or what I should be doing with this...? |
Ha yeah sorry I was trying to remove it before Melvin noticed, but I failed. Nothing to do at the moment - we're going to be assigning this directly to a C+, who will eventually need payment, so might as well stick around... but no action right now! |
Picking this up. |
Picking this up as C+ |
Job added to Upwork: https://www.upwork.com/jobs/~01df4dbeb24127ed89 |
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! |
oh hm it didn't register @mananjadhav . @ishpaul777 can you do the 🎀 thing? Maybe it needs that. |
🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @johnmlee101, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
i think thats becuase Manan got paid through New Dot ? |
oh maybe? that makes it easier if so. In any case, @mananjadhav you're assigned! |
FYI it looks like we send
etc. And another note, for Xero we are using updatePolicyXeroConnectionConfig which eventually calls UpdatePolicyConnectionConfiguration |
Okay let me know once we have these API on staging I'll start with the PR. |
Backend is merged, not yet deployed, but you can probably start working and it'll be up by the time testing is ready. Here are the relevant new commands, just to confirm:
Export commands:
Sync commands:
I grouped the sync and export ones that will need to be split up |
Spoke too soon, I guess - this is on staging now, so code away! |
@mananjadhav let us know how things are going! |
I should have the PR by tomorrow. |
I will raise the draft PR in a few hours. |
I had some system issues and now I am on a new system. I'll be redoing some of the work, so will raise a PR by end of day today. |
quick question @dangrous, I can see we have added App/src/libs/actions/connections/Xero.ts Lines 65 to 70 in 6d00670
Now for my commands In turn we're also calling |
I think |
Thanks for confirming. We'll need to do the same for sync and the error/pending fields methods. |
@mananjadhav, @dangrous, @VictoriaExpensify, @ishpaul777 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Update: @mananjadhav has a draft PR which is almost 90% ready for review just pending checklist and some conflicts, i'll review it over the weekend |
@dangrous I am getting an issue while executing web-sync-reimbursed-reports.mov |
Sorry for the delay on this @ishpaul777 ! I've found the issue and am raising a BE PR to fix momentarily (https://github.com/Expensify/Web-Expensify/pull/43460) |
@mananjadhav that issue should be fixed on staging! |
Is there anything else left to do here? |
This is on staging once deployed to prod then hold for 7 day regression period |
This was deployed to prod on 9/16. Stupid automation. |
It looks like this is ready for payment then 🤑 |
Payment summary: |
$250 approved for @mananjadhav |
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: @Issue Owner
Current Issue Owner: @VictoriaExpensifyThe text was updated successfully, but these errors were encountered: