Skip to content

[HOLD for payment 2024-04-15] IOU - IOU preview in the main chat does not support mark down, while IOU report supports it #39451

Description

@kbecciv

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 1.4.59-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to FAB > Request money > Manual.
  3. Request money from user with no unsettled request and include description with mark down.
  4. Note that the IOU preview in 1:1 DM does not support mark down.
  5. Create a second request with the same user.
  6. Go to IOU report.
  7. Note that the IOU preview of the first request in expense report supports mark down.

Expected Result:

Since IOU preview in IOU report (Step 6) supports mark down, the IOU preview in the main chat should also support mark down.

Actual Result:

The IOU preview in the main chat does not support mark down.

Workaround:

n/a

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6435885_1712081039309.20240403_015949.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @ishpaul777
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~019a357ce26a3a91d5
  • Upwork Job ID: 1780017603019825152
  • Last Price Increase: 2024-04-15

Activity

  1. melvin-bot commented on Apr 2, 2024

    @melvin-bot

    Triggered auto assignment to @aldo-expensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  2. github-actions commented on Apr 2, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  3. kbecciv commented on Apr 2, 2024

    @kbecciv
    Author

    We think that this bug might be related to #wave-collect - Release 1

  4. neonbhai commented on Apr 2, 2024

    @neonbhai
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    IOU preview in the main chat does not support mark down, while IOU report supports it

    What is the root cause of that problem?

    We don't use renderHTML to render the description in ReportPreview hence it displays as plain-text

    {shouldShowSubtitle && (
    <View style={styles.flexRow}>
    <View style={[styles.flex1, styles.flexRow, styles.alignItemsCenter]}>
    <Text style={[styles.textLabelSupporting, styles.textNormal, styles.lh20]}>{previewSubtitle || moneyRequestComment}</Text>
    </View>
    </View>
    )}

    What changes do you think we should make in order to solve the problem?

    We should use renderHTML to render the description like we do here:

    {shouldShowDescription && (
    <View style={[styles.breakWord, styles.preWrap]}>
    <RenderHTML html={`<muted-text>${parser.replace(merchantOrDescription)}</muted-text>`} />
    </View>
    )}

  5. added
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed
    ReviewingHas a PR in review
    on Apr 2, 2024
  6. 20 remaining items

  7. changed the title [-] IOU - IOU preview in the main chat does not support mark down, while IOU report supports it[/-] [+][HOLD for payment 2024-04-15] IOU - IOU preview in the main chat does not support mark down, while IOU report supports it[/+] on Apr 8, 2024
  8. melvin-bot commented on Apr 8, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.60-13 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-04-15. 🎊

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

    • @ishpaul777 requires payment (Needs manual offer from BZ)
  9. melvin-bot commented on Apr 8, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@ishpaul777] The PR that introduced the bug has been identified. Link to the PR:
    • [@ishpaul777] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@ishpaul777] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@ishpaul777] Determine if we should create a regression test for this bug.
    • [@ishpaul777] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@kadiealexander] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  10. melvin-bot commented on Apr 15, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@kadiealexander)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  11. added
    InternalRequires API changes or must be handled by Expensify staff
    on Apr 15, 2024
  12. melvin-bot commented on Apr 15, 2024

    @melvin-bot
  13. removed
    InternalRequires API changes or must be handled by Expensify staff
    on Apr 15, 2024
  14. deleted a comment from melvin-bot on Apr 15, 2024
  15. ishpaul777 commented on Apr 16, 2024

    @ishpaul777
    Contributor

    hey @kadiealexander The issue was create before the price drop https://expensify.slack.com/archives/C02NK2DQWUX/p1712250884549319, I think provious bounty $500 should be applicable here

  16. kadiealexander commented on Apr 17, 2024

    @kadiealexander
    Contributor

    Fixed, please accept.

  17. ishpaul777 commented on Apr 17, 2024

    @ishpaul777
    Contributor

    Thank you! Accepted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions