-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Markdown tables with 2 character dashes under headers do not render as tables #371
Comments
Why would you want to use only 2? |
Using the same number of characters as the header to create the divider, in this case, |
As long as you put as least 3 dashes, the table will always look the same.
render as
|
Yes, but I am raising the issue that GitHub users could construct tables in terms of my first example, and that is not displayed as an HTML table. |
Oh. I see. |
OK, thanks! Created vmg/redcarpet#418. |
Redcarpet does not render our Markdown. We use an internal closed-source gem, github-markdown. However, the three dashes are expected behavior. |
Are the three dashes required, and two is simply invalid? |
Oh my bad. The README.md is a bit confusing:
I assumed RedCarpet was rendering the Markdown without really checking the code :/ |
Reopening in light of new information from @gjtorikian. |
That's the interface gem, but underneath it still uses an actual Markdown implementation. It's not clear from the code which implementation that is, but my understanding is that it's Redcarpet. https://github.com/github/markup/blob/master/lib/github/markup/markdown.rb |
And we walk through all the Markdown implementations available to stop at the one that loads first: https://github.com/github/markup/blob/master/lib/github/markup/markdown.rb#L33-L39
Three (or more) dashes, yes. |
This is a minor issue -- but supporting the two character use case (and, maybe a single char as well) would be a nice touch for GitHub users. I ran into this during my workday today. |
Thanks for the request. I've logged it with our internal teams. |
Thanks! 🍰 |
not sure why the following table doesn't work: The source code:
It doesn't render as a table:
|
@greenlaw110 You need to remove the single space before each line. |
@pchaigno yes I just noticed that :-) |
…iter row Some time after [#371](github/markup#371) GFM relaxed constraints on the minimal number of required dashes in table delimiter row.
Some time after [#371](github/markup#371) GFM relaxed constraints on the minimal number of required dashes in table delimiter row.
In or around [#371](github/markup#371), GFM relaxed constraints on the minimal number of required dashes in table delimiter row. So we relax the constraints as well. To "compensate" for this change, we check the format of the delimiter row more thoroughly (although we still do *not* check number of cells in the delimiter row).
In or around [#371](github/markup#371), GFM relaxed constraints on the minimal number of required dashes in table delimiter row. So we relax the constraints as well. To "compensate" for this change, we check the format of the delimiter row more thoroughly (although we still do *not* check number of cells in the delimiter row).
In or around [#371](github/markup#371), GFM relaxed constraints on the minimal number of required dashes in table delimiter row. So we relax the constraints as well. To "compensate" for this change, we check the format of the delimiter row more thoroughly (although we still do *not* check number of cells in the delimiter row).
does not render as a table, whereas
does.
Is this expected behavior?
The text was updated successfully, but these errors were encountered: