Thinkmill / Thinkmill/keystatic
allow inline mdx fields in custom content components
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 159
- Avg merge
- 21h 41m
- Merged PRs (30d)
- 2
Description
it would be very cool if the following schema was supported:
content: fields.mdx({
label: "Content",
components: {
Widget: wrapper({
label: "Widget",
schema: {
title: fields.text({
label: "Title",
}),
summary: fields.mdx.inline({
label: "Summary",
}),
},
}),
},
}),
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the schema handling for fields.mdx and custom content components, then determine how fields.mdx.inline could be accepted inside a component schema. Done means the shown schema is supported and its inline Summary field works as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- content
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100