Skip to content

spectacle-mdx-loader: MDX component map lacks a lot of things that Markdown supports #1232

Open
@ryan-roemer

Description

@ryan-roemer

We have a discrepancy in code blocks in MD vs. MDX and likely other Spectacle core component support.

Example

For our MD example with pnpm start:md for the code page we have:

Screen Shot 2022-09-21 at 1 50 03 PM

For our MDX example with pnpm start:mdx for the code page with exact same sample we have:

Screen Shot 2022-09-21 at 1 50 08 PM

Cause

Our Markdown component and related components do a lot more things than our mdxComponentMap does that we pass into MDX.

Work

See if we can expand mdxComponentMap to something more general that ideally doesn't rejigger core Spectacle too much.

Metadata

Metadata

Assignees

No one assigned

    Labels

    🐛 BugIssues or PRs that report or fix a bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions