Skip to content

Send optimistic transactionThreadReportID and createdReportActionIDForThread with API commands RequestMoney, CreateDistanceRequest, CompleteSplitBill, SendMoney #31411

Description

@cead22
  • Design Doc
  • The back end changes will be done in a separate issue
  • Update getMoneyRequestInformation to generate an optimistic transactionThreadReportID and createdReportActionIDForThread using ReportUtils.buildTransactionThread
    • Here's a commit with a proof-of-concept for these changes
      • We should make sure we're updating optimisticData with both values correctly
      • Ignore the comment // TODO add logic to create transaction thread for each DM between split participants
  • Update getSendMoneyParams like getMoneyRequestInformation, send transactionThreadReportID and createdReportActionIDForThread, and add this to the request's optimisticData
  • For the case of CompleteSplitBill where the user enters details manually before SmartScan finishes, we’ll generate random reportIDs in the client
    • Create a transactionThread and a created report action optimistically before the call to buildOnyxDataForMoneyRequest inside completeSplitBill like we do in getMoneyRequestInformation
    • Pass optimisticCreatedAction.reportID as the last param to the buildOnyxDataForMoneyRequest call
    • Add transactionThreadReportID: transactionThread.reportID and createdReportActionIDForThread: optimisticCreatedAction.reportActionID to the params object we pass to API.write(‘CompleteSplitBill’, {params})

Activity

  1. cead22 commented on Nov 16, 2023

    @cead22
    ContributorAuthor

    @cdanwards can you comment here so I can assign you?

  2. cdanwards commented on Nov 16, 2023

    @cdanwards
    Contributor

    Commenting for Assignment

  3. melvin-bot commented on Nov 20, 2023

    @melvin-bot

    @cdanwards Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  4. melvin-bot commented on Nov 22, 2023

    @melvin-bot

    @cdanwards Eep! 4 days overdue now. Issues have feelings too...

  5. cdanwards commented on Nov 22, 2023

    @cdanwards
    Contributor

    No update.

  6. melvin-bot commented on Nov 28, 2023

    @melvin-bot

    @cdanwards Huh... This is 4 days overdue. Who can take care of this?

  7. cdanwards commented on Nov 29, 2023

    @cdanwards
    Contributor

    Next in line for work

  8. 56 remaining items

  9. melvin-bot commented on Feb 23, 2024

    @melvin-bot
  10. cead22 commented on Feb 23, 2024

    @cead22
    ContributorAuthor

    @johncschuster please issue payment to C+ @situchan for PR review. Thanks!

  11. melvin-bot commented on Feb 27, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  12. johncschuster commented on Feb 27, 2024

    @johncschuster
    Contributor

    @situchan I've extended an invite, here. Can you accept that? Thanks!

  13. johncschuster commented on Mar 6, 2024

    @johncschuster
    Contributor

    @cead22 it looks like this issue was linked to a deploy blocker. Has that been resolved, or do I need to wait on issuing payment?

  14. situchan commented on Mar 6, 2024

    @situchan
    Contributor

    This issue was mentioned here which made Melvin post above message. Not regression.

  15. johncschuster commented on Mar 8, 2024

    @johncschuster
    Contributor

    Payment Summary:

    Contributor: @cdanwards - Contractor
    C+ Reviewer: @situchan - $500 - Upwork job offer

  16. johncschuster commented on Mar 8, 2024

    @johncschuster
    Contributor

    Paid!

  17. BiswaJK commented on Mar 21, 2024

    @BiswaJK
  18. melvin-bot commented on Mar 21, 2024

    @melvin-bot

    📣 @BiswaJK! 📣
    Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
    Please follow these steps:

    1. Make sure you've read and understood the contributing guidelines.
    2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
    3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions