question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[HOLD for payment on July 1] Markdown - Quote markdown behaviour is not correct

See original GitHub issue

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


Expected Result:

Text should be displayed like this:

  1. quote indents on subsequent lines should be combined (but separated if there is a blank line between)
  2. quoting a blank line should be fine

Actual Result:

Text in e.cash is displayed like this:

Action Performed:

  1. Log in to expensify.cash
  2. Navigate to a conversation
  3. Insert this text and press enter
> This is a one line quote

> This is a two line quote
> And this is the second line

> This is a three line quote
>
> With an empty line in the middle that has no space after the chevron

> This is another three line quote
>  
> But this time there's a space after the middle chevron

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platform:

Where is this issue occurring?

Web ✔️ iOS Android Desktop App Mobile Web

Version Number: 1.0.35-0

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Check images above.

Expensify/Expensify Issue URL:

View all open jobs on Upwork


From @quinthar https://expensify.slack.com/archives/C01GTK53T8Q/p1619989048284300

Quote intends are sorta weird; we should copy Slack’s behavior. Here’s the raw text: With an empty line in the middle that has no space after the chevron This is another three line quote

But this time there’s a space after the middle chevron

This is how it comes out (correctly) on Slack, and (incorrectly) on E.cash. In particular:

  1. quote indents on subsequent lines should be combined (but separated if there is a blank line between)
  2. quoting a blank line should be fine

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:27 (22 by maintainers)

github_iconTop GitHub Comments

1reaction
stephanieelliottcommented, Jul 1, 2021

Job paid and closed in Upwork!

1reaction
laurenreidexpensifycommented, Jun 17, 2021

@stephanieelliott I’m OOO til 5 July, so am reassigning my chores. Thanks.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Basic Syntax - Markdown Guide
Overview. Nearly all Markdown applications support the basic syntax outlined in the original Markdown design document. There are minor variations and ...
Read more >
Formatting text with Markdown - Zendesk help
Markdown is a simple markup language you can use to easily add formatting, links, and images to plain text. You can use it...
Read more >
cheat down - MamaFood
This Markdown cheat sheet provides a quick overview of all the Markdown syntax You can download this cheat sheet as a Markdown file...
Read more >
The Ultimate Markdown Cheat Sheet | by Mahbub Zaman
What is Markdown? Markdown is a way of writing rich-text (formatted text) content using plain text formatting syntax. From this post, you'll ...
Read more >
Using Markdown in Airtable
Markdown is a lightweight and readable syntax used for formatting text. Formatting text can be useful in Airtable when you are looking to......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found