Comments (4)
Rather than having .jsx
specific syntax (assuming inline JSX support), we should have different component contexts for different syntaxes. So when you pass in your component scope you can specify components like so:
import Markdown from '@c8r/markdown'
import {
Text,
Heading,
CodeBlockJSX,
CodeBlockHTML
} from './ui'
// ...
<Markdown
text={md}
components={{
p: Text.p,
h1: Heading.h1,
codeBlock: {
jsx: CodeBlockJSX,
html: CodeBlockHTML
}}
/>
from mdx.
I wonder about the inlining js portion, perhaps that can be left out? Or perhaps it should be JSX {}
syntax?
from mdx.
If a markdown document is imported with a custom babel loader, we need to consider the best way to provide a component mapping to the core library. For example, a trivial component mapping might be:
{
a: Link,
p: Text,
h1: Heading,
// ...
}
One option could be using a context provider:
import React from 'react'
import { MdProvider } from '@compositor/markdown'
import Document from './document.mdx'
import * as ui from './ui'
export default () =>
<MdProvider components={ui}>
<Document />
</MdProvider>
from mdx.
Preliminary import, component mapping, and inlined jsx support completed ✅
from mdx.
Related Issues (20)
- mdx 2.3.0 + remark-gfm 4.0.0 breaks tables HOT 6
- no MdastImportVisitor found for html HOT 1
- mdx 3 converts component elements to p tag HOT 4
- Allow javascript expression in markdown links [](myvar.foo}) HOT 2
- `@mdx-js/rollup` stops working on Vite v5 HOT 13
- created a new recma plugin `recma-mdx-escape-missing-components` HOT 11
- created a new recma plugin `recma-mdx-change-props` HOT 6
- Patch version 3.0.0 to 3.0.1 killed all admonitions HOT 2
- react hmr (fast refresh) breaks when deleting all content of a mdx file HOT 5
- Invalid hook call when using react class component in MDX HOT 4
- Useless/bad error message when forgetting to close an element HOT 3
- MDXProvider is invalid after processSync processing when {jsxImportSource: 'vue', providerImportSource: '@mdx-js/vue'} is configured. HOT 2
- Return a VFile with an appropriate extension in the path HOT 5
- Type Error on jsx type with react jsx runtime HOT 7
- Make the compiler aware of custom components HOT 2
- MDXProvider not working as expected. HOT 2
- Unable to parse custom heading ids HOT 4
- When importing .mdx file in a .stories.tsx file: Unexpected `FunctionDeclaration` in code: only import/exports are supported HOT 3
- React 19 types compatibility HOT 4
- Dynamic linked heading does not interpolate link properly HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mdx.