[x] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
[x] I have read the documentation and cannot find an answer.
Describe the bugjsxPlugin introduces handling of the JSX which includes expressions as well. When I want to use an expression within MDX, it correctly works for inline expressions. E.g.:
This is inline {expression}
Internally, it is correctly "identified" as mdxTextExpression, therefore it is handled correctly. But once it stands alone in the line, mdast will identify this expression as mdxFlowExpression which is correct as well, but jsxPlugin does not have a visitor for such type of expression. So it results in the error.
Reproduction
Example of the erroneous MDX:
This is an example of a line
{expression}
To Reproduce
You can use the MDX content from above.
Expected behavior
It should correctly consume mdxFlowExpression as it does with mdxTextExpression.
Additional context
I will open PR to fix this behavior in a few moments...
Pre-check
Describe the bug
jsxPluginintroduces handling of the JSX which includes expressions as well. When I want to use an expression within MDX, it correctly works for inline expressions. E.g.:Internally, it is correctly "identified" as
mdxTextExpression, therefore it is handled correctly. But once it stands alone in the line,mdastwill identify this expression asmdxFlowExpressionwhich is correct as well, butjsxPlugindoes not have a visitor for such type of expression. So it results in the error.Reproduction Example of the erroneous MDX:
To Reproduce You can use the MDX content from above.
Expected behavior It should correctly consume
mdxFlowExpressionas it does withmdxTextExpression.Additional context I will open PR to fix this behavior in a few moments...