-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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-05-09] Mark Down - Mark down doesn't work for task description after saving #41422
Comments
Triggered auto assignment to @srikarparsi ( |
👋 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:
|
@srikarparsi FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #vip-vsp |
ProposalPlease re-state the problem that we are trying to solve in this issue.Mark Down - Mark down doesn't work for task description after saving What is the root cause of that problem?It's because we are escaping it. We should only escape urls. but due to
What changes do you think we should make in order to solve the problem?Instead of false we should change it to true
Also remove
Solution 2 App/src/components/ReportActionItem/TaskView.tsx Lines 153 to 154 in 8661f6a
What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.Mark down doesn't work for task description after saving. What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?We don't need to pass shouldEscapeText, we can simply remove the below line:
|
Thanks for the proposals. Please make sure to link to the offending PR that caused the regression when you can identify it, in this case it looks like it was #41096. Going to test the proposals shortly. |
Thanks guys, I'm going to handle this internally because it requires changing some additional values for the onboarding tasks. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.69-2 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-05-09. 🎊 |
This was all handled internally, closing. |
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.69-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The description renders the markdown
Actual Result:
The description field doesn't render the appropriate markdown text
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6467994_1714573165721.bandicam_2024-05-01_17-15-16-315.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: