Support for fenced code block info string

[arobase-che]

Hi \o

The discussion is on the corresponding issue #342

Spoiler: It's about info string ;)

💘

[wooorm]

Build failed for some reason, I restarted it and now it’s green again!

[arobase-che]

¯_(ツ)_/¯

[wooorm]

@arobase-che Could you update the code here to match syntax-tree/mdast#22?

[arobase-che]

Humm, it's already done. See that comment. I updated both the same day (night ...).

[wooorm]

@arobase-che Sorry, missed it! Soooo, I was in the process of merging this, but hmm, from what I read in the commonmark spec they call the whole thing the info string (I still like info instead of info string). However, as we’re removing the lang from it, I’m not sure info is still fitting. Would it make sense to use meta instead? I’m not sure where I saw it today, but I like it:

~~~js foo bar baz
   ^^^^^^^^^^^^^^ info
      ^^^^^^^^^^^ meta
   ^^ lang
console.log('!')
~~~

/CC @Hypercubed

[ChristopherBiscardi]

Would love to see this get merged as we're getting requests for support in downstream projects (gatsby-mdx and mdx).

Is there anything I can do to help move this along? It looks like it might just need final review.

[arobase-che]

Oups !
I forgot to update the mdast description ! It's now done.

Normaly after that, it will be merged soon. @wooorm is about to publish a new version.

[ChristianMurphy]

LGTM, thanks @arobase-che! 🙇

[wooorm]

Hey this looks great! I refactored the code a bit so as to not use .trim() (which removed javascript white-space, which is not the same as markdown white-space). This unearthed that we needed some more fixtures (e.g., for multiple white-space, or for tabs), which I added.

This looks great, thanks @arobase-che!

[wooorm]

Landed!