React-markdown: suggest: support table
suggest: support GFM(GitHub flavored markdown) tables: https://help.github.com/articles/organizing-information-with-tables/
| Command | Description |
| --- | --- |
| `git status` | List all *new or modified* files |
| `git diff` | Show file differences that **haven't been** staged |
sinkcup
All 32 comments
These are pretty important. Would love to see!
ztratar
on 15 Mar 2016
I'd love to support them, but commonmark does not include them in the spec. I'm going to start experimenting with an alternative markdown parser. It might take a while to complete, since it'll almost be a complete rewrite, however.
rexxars
on 15 Mar 2016
+1
Can you please share the status on this ?
aviadl
on 29 Mar 2016
Have no gotten much farther on this. Have experimented with alternative markdown parsers, and know that it's doable, it's just a matter of getting time to do it. Right now other projects are taking up most of my time. Don't want to give out estimates for open-source work as it totally depends on how much free time I have to work on it, which varies.
rexxars
on 29 Mar 2016
+1 For this
Really need the table working
TakanashiOuken
on 15 Jun 2016
+1 for table... really need it... please please add it
sauravskumar
on 10 Aug 2016
https://github.com/chjj/marked this markdown parser has support for tables...
sauravskumar
on 14 Aug 2016
This was pretty damn awesome until I almost finished what I was working on, tried to use a table, and it fell flat on its face 馃槩
Switched over to remarkable and highlight.js as seen in Facebook's own Markdown React example.
Swivelgames
on 26 Sep 2016
+1 For tables
sasha240100
on 7 Oct 2016
tuchk4
on 21 Oct 2016
Just thought I'd let you guys know that I've started working on the next major release of react-markdown, which will switch from commonmark to markdown, thus enabling tables (among other things).
There will be some breaking changes to the API, but nothing that should take too long to fix.
rexxars
on 26 Oct 2016
@rexxars
Nice to hear, but which library in particular do you intend to use, and why abandon CommonMark? Why not markdown-it, another CM-compatible library, acknowledged by jgm, the main guy behind CM?
In my use case, if you were to use something non-CM, the difference would probably be minimal, since the only user-generated content we have is comments, which people rarely format, and the rest can be adjusted relatively easily. But what about those with gigabytes of Markdown data, which might render differently?
alecmev
on 26 Oct 2016
@jeremejevs I'll continue to maintain commonmark-react-renderer, which to be fair is pretty much where all the logic of react-markdown resides. In hindsight, I should have named this module react-commonmark, since that's what it currently renders. Perhaps now would be a good time to fork and publish just that.
rexxars
on 26 Oct 2016
@rexxars I understand that the current implementation can and will be maintained, and that nobody is forced to switch, but it would be nice to have both CM-compatibility _and_ tables. That lets existing users upgrade easily, and, on the religious front, we can remain invested into a proper standard.
alecmev
on 26 Oct 2016
@jeremejevs As in; being able to opt-out of non-commonmark types?
Are there any compatibility issues in particular you're worried about? For most people, I'd think that the move would result in little or no changes in the rendered output.
rexxars
on 26 Oct 2016
@rexxars As in rendering everything the same way commonmark.js would. There are no issues in particular I'm worried about, I just know for sure that most renderers differ in one way or another. Take a look at Babelmark's examples of divergences (look for markdown-it as a representative of CommonMark).
alecmev
on 26 Oct 2016
Just curious about the status of the implementation of tables, are any rough goals ?
tbillington
on 8 Jan 2017
Anyone with a simple use-case and just needs table support, I found react-remarkable to be a light-weight solution that's easily swappable with react-markdown.
martellaj
on 10 Jan 2017
@tbillington Been caught up with real-life lately, but I'm going to work on react-markdown this weekend, hoping to get closer.
rexxars
on 13 Jan 2017
@rexxars Which table format would you implement, github style?
tbillington
on 13 Jan 2017
Yup, Github-style.
rexxars
on 13 Jan 2017
+1 for tables! thanks!
agustinlg
on 3 Feb 2017
@rexxars do you have an update on this?
sichvoge
on 3 Feb 2017
Been in the hospital for the past week, and I am in no fit state to code right now. It's pretty close, but not willing to give estimates based on health
rexxars
on 3 Feb 2017
@rexxars Good luck with that! Don't worry about this issue and take your time. Nobody is forcing you. :smile:
FlorianWendelborn
on 3 Feb 2017
Agree to @dodekeract. Health should always be first priority! Thanks for all your good work.
sichvoge
on 5 Feb 2017
@rexxars Sorry to hear. Thanks for all your hard work on this.
And I'm with them ^ take care of yourself first!
simonbuerger
on 6 Feb 2017
Like everyone, I hope everything going well. You do a great job and your module rocks! Looking forward to see tables implementation. Take care of yourself.
pnepe6
on 2 Nov 2017
Awesome stuff! Really need github-style table support to display some release notes in an app I'm working on. Looking forward to it!
simen
on 10 Nov 2017
The new release candidate for v3 has table support. Please read this issue for more information. Please give it a go and let me know if you encounter issues.
rexxars
on 11 Nov 2017
Closing this issue to make it easier for me to keep track of pending issues.
rexxars
on 11 Nov 2017
This is great, I really need tables as well.
The other thing I noticed is that
doesn't render as expected.
rwlaschin
on 15 Feb 2020
Related issues
damianobarbati
路
3Comments
IonicaBizau
路
4Comments
dekryptic
路
3Comments
zhenyulin
路
3Comments
ghost
路
4Comments
Most helpful comment
Been in the hospital for the past week, and I am in no fit state to code right now. It's pretty close, but not willing to give estimates based on health