Skip to content
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-10-30] [HOLD for payment 2024-10-29] [3rd Party Feeds] Implement API calls for 3rd part workspace feeds v1 #49690

Open
dylanexpensify opened this issue Sep 25, 2024 · 39 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Engineering NewFeature Something to build that is a new item. Task Weekly KSv2

Comments

@dylanexpensify
Copy link
Contributor

dylanexpensify commented Sep 25, 2024

Coming from this thread, we have some clean up to-dos for the Third-party workspace feeds v1 initiative.

Issue OwnerCurrent Issue Owner: @strepanier03
Copy link

melvin-bot bot commented Sep 25, 2024

Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.

@VickyStash
Copy link
Contributor

Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.

@robertjchen
Copy link
Contributor

robertjchen commented Sep 25, 2024

WorkspaceCompanyCardsPage.tsx

  • OpenPolicyCompanyCardsPage(policyID)

WorkspaceCompanyCardsListHeaderButtons.tsx

  • AssignCard(policyID, bankName, encryptedCardNumber, email, startDate, reportActionID)

WorkspaceCompanyCardsSettingsPage.tsx

WorkspaceCompanyCardFeedSelectorPage.tsx

WorkspaceMemberNewCardPage.tsx

  • OpenPolicyCompanyCardsFeed(policyID, bankName)
  • SetCardExportAccount(cardID, exportAccountDetails)
  • SetCardName(cardID, cardName)

CardSelectionStep.tsx

  • OpenPolicyCompanyCardsFeed() called earlier in the flow should already load the list of cards 🤔

@narefyev91
Copy link
Contributor

Hi, I'm Nicolay from Callstack - expert contributor group - will help here as well (from tomorrow).
Will pick:

  • WorkspaceCompanyCardsSettingsPage.tsx
  • WorkspaceMemberNewCardPage.tsx
    OpenPolicyCompanyCardsFeed(policyID, bankName)
    SetCardExportAccount(cardID, exportAccountDetails)
    SetCardName(cardID, cardName)

@joekaufmanexpensify
Copy link
Contributor

Assigned!

@VickyStash
Copy link
Contributor

@robertjchen I have a question about reportActionID for this API call:
AssignCard(policyID, bankName, encryptedCardNumber, email, startDate, reportActionID).

Is it for this message? Should I optimistically create it?
image

I'm asking cause it looks like we don't create similar messages optimistically while issuing Expensify Cards.
^^ @mountiny

@robertjchen
Copy link
Contributor

Interesting! That's a good point- if these messages are not being optimistically created, then the reportActionID is not needed 👍

@mountiny
Copy link
Contributor

@robertjchen I think it's a bit different thought, right? With Expensify cards, we have to talk to Marqeta, a third-party service, and so there is a higher chance of the call with fail, so we do not create the actions optimistically. In this case, when we already have the list of the available cards, there are fewer things that can cause it to fail, so I think we could consider adding these optimistically; what do you think, @robertjchen?

@robertjchen
Copy link
Contributor

That makes sense, that context definitely helps!

Since we already have all the info we need in Onyx at time of assignment, we can definitely do it optimistically which would make for a better user experience

@mountiny
Copy link
Contributor

@VickyStash Feel free to add the optimistic reportActionID param to the api call and create the action optimistically and we can add it to BE

@joekaufmanexpensify joekaufmanexpensify changed the title [Clean up] Implement API calls for 3rd part workspace feeds v1 [3rd Party Feeds] Implement API calls for 3rd part workspace feeds v1 Sep 26, 2024
@VickyStash
Copy link
Contributor

@robertjchen Could you say what action name this optimistic report action should have? I'm talking about the one created during AssignCard API call.

@robertjchen
Copy link
Contributor

@VickyStash It would be CARDASSIGNED

@VickyStash
Copy link
Contributor

I've prepared a Draft PR with:

  • AssignCard API call
  • Plain implementation of RequestFeedSetup API call
  • Support of CARDASSIGNED report action display
  • TODOs resolution

@robertjchen Please, let us know when RequestFeedSetup is deployed so we can start extensive testing of the functionality with the real data.

@melvin-bot melvin-bot bot removed the Overdue label Sep 30, 2024
@robertjchen
Copy link
Contributor

Yes, it appears to be under review at the moment 👍

@dylanexpensify
Copy link
Contributor Author

Making progress

@melvin-bot melvin-bot bot removed the Overdue label Oct 3, 2024
@VickyStash
Copy link
Contributor

Updates:

  • Updated params passed to RequestFeedSetup
  • Waiting for API fixes

@melvin-bot melvin-bot bot added the Overdue label Oct 7, 2024
@dylanexpensify dylanexpensify removed their assignment Oct 15, 2024
@dylanexpensify dylanexpensify added the NewFeature Something to build that is a new item. label Oct 15, 2024
Copy link

melvin-bot bot commented Oct 15, 2024

Triggered auto assignment to @strepanier03 (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

@dylanexpensify
Copy link
Contributor Author

Reassigning as I head to parental leave next week! Thanks Sheena!

@allgandalf
Copy link
Contributor

♻️ PR was merged

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Oct 18, 2024
@melvin-bot melvin-bot bot changed the title [3rd Party Feeds] Implement API calls for 3rd part workspace feeds v1 [HOLD for payment 2024-10-29] [3rd Party Feeds] Implement API calls for 3rd part workspace feeds v1 Oct 22, 2024
Copy link

melvin-bot bot commented Oct 22, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Oct 22, 2024
Copy link

melvin-bot bot commented Oct 22, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.51-4 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-10-29. 🎊

For reference, here are some details about the assignees on this issue:

Copy link

melvin-bot bot commented Oct 22, 2024

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:

  • [@allgandalf] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
  • [@strepanier03] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

@allgandalf
Copy link
Contributor

No checklist here, this belongs to a project, Only payment remains 🙏 (This is a 3rd party feed project and not direct feed so...)

@mountiny
Copy link
Contributor

mountiny commented Oct 22, 2024

$250 to @allgandalf

@allgandalf
Copy link
Contributor

🤣 i wonder what you are doing in 🇯🇵 these days

@mountiny
Copy link
Contributor

psst

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Oct 23, 2024
@melvin-bot melvin-bot bot changed the title [HOLD for payment 2024-10-29] [3rd Party Feeds] Implement API calls for 3rd part workspace feeds v1 [HOLD for payment 2024-10-30] [HOLD for payment 2024-10-29] [3rd Party Feeds] Implement API calls for 3rd part workspace feeds v1 Oct 23, 2024
Copy link

melvin-bot bot commented Oct 23, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.52-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-10-30. 🎊

For reference, here are some details about the assignees on this issue:

Copy link

melvin-bot bot commented Oct 23, 2024

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:

  • [@allgandalf] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
  • [@strepanier03] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

@allgandalf
Copy link
Contributor

No checklist, payment summary here

@mountiny
Copy link
Contributor

New feature so no checklist needed here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Engineering NewFeature Something to build that is a new item. Task Weekly KSv2
Projects
Status: Release 3: Fall 2024 (Nov)
Development

No branches or pull requests

8 participants