Correct descriptions/tags in Table of components

[mrm007]

Fixed tags for mdast code, inlineCode and thematicBreak types.

Preview here: https://mdx-git-patch-1.mdx.vercel.app/table-of-components

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/mdx/mdx/m94vwpjp2
✅ Preview: https://mdx-git-patch-1.mdx.vercel.app

[wooorm]

Did you confirm that code is for inline code? I believe we have an inlineCode “element” for inline code:

mdx/packages/mdx/mdx-ast-to-mdx-hast.js

Line 13 in 889eb4b

tagName: 'inlineCode',

(also on next branch)

[mrm007]

@wooorm you're right, of course. Fixed that row in the table.

[wooorm]

thanks!

I’ve just been doing some work in this repo, which gave me some new insights on this table. Sure MDX supports markdown, but the components in MDXProvider can be anything. If you have an <Icon /> in MDX, you can have an Icon in components. Something like that might be good to mention here.
A different insight is that while the source is markdown-esque, and thus linking to mdast has some value, but it’s actually more HTML-like: <code> is also used because markdown code maps to pre and code.

So, for this PR: I think code has to be added back. And if you’d like to do more, although it could also be a new PR, a bigger refactor of this table, what it links to, and surrounding prose, might be helpful!

[johno]

Added back code, so going to go ahead and merge this. We should prolly create another issue to refactor this table in its entirety.