[3rd Party Feeds] Implement API calls for 3rd part workspace feeds v1

[dylanexpensify]

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

[melvin-bot]

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

[VickyStash]

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

[robertjchen]

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]

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]

Assigned!

[VickyStash]

@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?

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

[robertjchen]

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

[mountiny]

@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]

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]

@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

[VickyStash]

@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]

@VickyStash It would be CARDASSIGNED

[VickyStash]

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.

[robertjchen]

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

[dylanexpensify]

Making progress

[VickyStash]

Updates:

• Updated params passed to RequestFeedSetup
• Waiting for API fixes

[dylanexpensify]

TY @VickyStash!