Markdown parsing in parameters

[n9]

<NewsList empty={<>
    No news found. Try to check [calendar](/calendar)
</>} />

outputs

No news found. Try to check [calendar](/calendar)

Is this by design? What's the reason for it?

[remcohaszing]

Since MDX is hybrid language between markdown and JavaScript(X), we need to make trade-offs. Props values are parsed as JavaScript expressions. Your suggestion is to parse props values as MDX. This means for example the following MDX:

<Element hello={'World'} />

would now be equivalent to the following JSX:

<Element hello={<p>'World'</p>} />

I think this would come as a total surprise to users.

Coincidentally, I wrote a nice little related blog post some time ago. You might like that pattern.

[n9]

Coincidentally, I wrote a nice little related blog post some time ago. You might like that pattern.

Thank you for the blog post!

Your suggestion is to parse props values as MDX. This means for example the following MDX: ...

I would keep the current behavior, where:

<Element hello={'World'} />

is equivalent to:

<Element hello={'World'} />

But whenever node children are encountered, I would switch back to MDX. So:

<Element hello={<p>*Big* World</p>} />

would be equivalent to:

<Element hello={<p><em>Big</em> World</p>} />

and

<Element hello={<>*Big* World</>} />

would be equivalent to:

<Element hello={<><em>Big</em> World</>} />

I think this would come as a total surprise to users.

I have the opposite experience. It is surprising that content between tags is no longer parsed as MDX.