-
Notifications
You must be signed in to change notification settings - Fork 3k
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-12-30] [Awaiting payment][$250] Mark down - The sent message containing two > does not display double quote mark down #45154
Comments
Triggered auto assignment to @pecanoro ( |
👋 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:
|
@pecanoro 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 |
Caused by #44262 |
Confirmed and posted in the PR, we probably need to assign the people to fix it! |
Oh, but maybe we don't need to hold on this as it only happens when you do >> which it's an edge case |
Yeah lets not hold on this, we have to get to higher version of the markdown library and this does not seem that big issue Please feel free to reassign to me, happy to handle this with swm or community upstream |
I think @BrtqKr will be the best person to help you here since he was the one working on block quotes 🙌🏻 |
Blockquote requires a space following it. If there are two blockquotes, they still need to be separated with a space. This was meant to allow empty lines to be treated as a part of the blockquote and prevent some of the issues with treating '>' as a blockquote unintentionally. I think this should go the other way - the input shouldn't show that this would result in a blockquote. |
@BrtqKr Let me know if I am following correctly, the problem here is that the composer should not show the preview of the markdown, right? |
@JmillsExpensify, @pecanoro, @Pujan92, @Skalakid, @BrtqKr Eep! 4 days overdue now. Issues have feelings too... |
#53627 has been merged so this issue should be resolved now. |
@JmillsExpensify I think the only thing left here is pay @Pujan92 for the review |
@JmillsExpensify, @pecanoro, @Pujan92, @Skalakid, @BrtqKr Huh... This is 4 days overdue. Who can take care of this? |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.77-6 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-12-30. 🎊 For reference, here are some details about the assignees on this issue: |
@Pujan92 @JmillsExpensify @Pujan92 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
@JmillsExpensify, @pecanoro, @Pujan92, @Skalakid, @BrtqKr Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Payment Summary
BugZero Checklist (@JmillsExpensify)
|
Payment summary above is correct. @Pujan92 do you mind completing the BZ checklist? |
Regression Test Proposal
|
@JmillsExpensify, @pecanoro, @Pujan92, @Skalakid, @BrtqKr Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@JmillsExpensify, @pecanoro, @Pujan92, @Skalakid, @BrtqKr 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
$250 approved for @Pujan92 |
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: 9.0.6-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 sent message containing two > will display double quote mark down
Actual Result:
The sent message containing two > does not display double quote mark down
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6537871_1720617437950.double_quote.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @JmillsExpensifyUpwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: