You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Strikethrough text is not working as expected if there's a space before the ~ #2846
When using multiple ~ in chat, markdown treats them as strikethrough. When there is a space before the second ~ we shouldn't use that to denote the markdown.
changed the title [-]Strikethrough text is not working as expected if there's a space before the ~[/-][+][HOLD for payment on July 9] Strikethrough text is not working as expected if there's a space before the ~[/+]on Jul 3, 2021
changed the title [-][HOLD for payment on July 9] Strikethrough text is not working as expected if there's a space before the ~[/-][+]Strikethrough text is not working as expected if there's a space before the ~[/+]on Jul 16, 2021
Activity
MelvinBot commentedon May 13, 2021
Triggered auto assignment to @sophiepintoraetz (
AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.sophiepintoraetz commentedon May 13, 2021
Copied the text and performed Step 2 in the web version and was able to reproduce:

MelvinBot commentedon May 13, 2021
Triggered auto assignment to @nickmurray47 (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.38 remaining items
[-]Strikethrough text is not working as expected if there's a space before the ~[/-][+][HOLD for payment on July 9] Strikethrough text is not working as expected if there's a space before the ~[/+]Jag96 commentedon Jul 3, 2021
Reopening to keep track of payment
puneetlath commentedon Jul 10, 2021
Paid.
[-][HOLD for payment on July 9] Strikethrough text is not working as expected if there's a space before the ~[/-][+]Strikethrough text is not working as expected if there's a space before the ~[/+]mallenexpensify commentedon Jul 16, 2021
@parasharrajat per this Slack thread, looks like we have a regression so I'm reopening
When markdown is used for only one character, it's not working correctly
https://files.slack.com/files-pri/T03SC9DTT-F0291KKFEHW/image.png
parasharrajat commentedon Jul 17, 2021
PR is up Expensify/expensify-common#395 for regression.
puneetlath commentedon Jul 19, 2021
Looks like that PR was merged, so going to go ahead and close this.
parasharrajat commentedon Jul 19, 2021
Ah, Need to update the ref here in E.cash.
parasharrajat commentedon Aug 4, 2021
Coming from slack thread https://expensify.slack.com/archives/C01GTK53T8Q/p1628107138154400. We might need to consider the Parsing for
~. It is not yet confirmed. Thankspuneetlath commentedon Aug 9, 2021
Ok, let's open a new issue if we decide we need to make a change. Thanks!