Skip to content

feat(MarkdownEditor): support custom toolbar tools - #2781

Open
TimAufdemKampe wants to merge 8 commits into
mainfrom
2538-custom-buttons-in-markdowneditor
Open

feat(MarkdownEditor): support custom toolbar tools#2781
TimAufdemKampe wants to merge 8 commits into
mainfrom
2538-custom-buttons-in-markdowneditor

Conversation

@TimAufdemKampe

@TimAufdemKampe TimAufdemKampe commented Aug 5, 2026

Copy link
Copy Markdown
Member

Related to #2538

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Coverage Report for ./packages/components/

Status Category Percentage Covered / Total
🔵 Lines 75.47% 600 / 795
🔵 Statements 75.21% 613 / 815
🔵 Functions 77.38% 130 / 168
🔵 Branches 65.85% 272 / 413
File Coverage
File Stmts Branches Functions Lines Uncovered Lines
Changed Files
packages/components/src/components/propTypes/index.ts 100% 100% 100% 100%
Generated in workflow #6075 for commit a5dd810 by the Vitest Coverage Report Action

@TimAufdemKampe
TimAufdemKampe force-pushed the 2538-custom-buttons-in-markdowneditor branch 2 times, most recently from 64a47a3 to b7f46bc Compare August 5, 2026 07:30
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🚀 Preview Deployment

Preview environments are ready:

Type URL
docs pr-2781.docs.review.flow-components.de
storybook pr-2781.storybook.review.flow-components.de

Images:

  • docs: ghcr.io/mittwald/flow/docs:pr-2781
  • storybook: ghcr.io/mittwald/flow/storybook:pr-2781

@TimAufdemKampe
TimAufdemKampe force-pushed the 2538-custom-buttons-in-markdowneditor branch from b7f46bc to 2a22a78 Compare August 5, 2026 07:49

@Jan-Eimertenbrink Jan-Eimertenbrink left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mir sind in der Doku schon mal ein paar kleinigkeiten aufgefallen. Technisch wird das am besten ein Dev reviewen. Mir ist noch aufgfallen, dass wir generell noch mal nach dem responsiven Verhalten der Komponente schauen müssen. Dazu mache ich aber ein extra issue

Comment thread apps/docs/src/content/04-components/form-controls/markdown-editor/overview.mdx Outdated
Comment thread apps/docs/src/content/04-components/form-controls/markdown-editor/overview.mdx Outdated
Comment thread apps/docs/src/content/04-components/form-controls/markdown-editor/guidelines.mdx Outdated
Comment thread apps/docs/src/content/04-components/form-controls/markdown-editor/guidelines.mdx Outdated
Comment thread apps/docs/src/content/04-components/form-controls/markdown-editor/guidelines.mdx Outdated
Comment thread apps/docs/src/content/04-components/form-controls/markdown-editor/guidelines.mdx Outdated
@Lisa18289

Copy link
Copy Markdown
Member

unter remote-react-components sollte noch ein Screenshot Test ergänzt werden

Comment thread packages/components/src/components/MarkdownEditor/MarkdownEditor.tsx Outdated
Comment thread packages/components/src/components/MarkdownEditor/MarkdownEditor.tsx Outdated
@Jan-Eimertenbrink Jan-Eimertenbrink linked an issue Aug 6, 2026 that may be closed by this pull request
@mfal mfal added the update-screenshots Label a PR to update the screenshots used for visual regression testing label Aug 7, 2026
@github-actions github-actions Bot removed the update-screenshots Label a PR to update the screenshots used for visual regression testing label Aug 7, 2026
Co-authored-by: mfal <4696750+mfal@users.noreply.github.com>
<MarkdownEditor rows={1} isDisabled>
<Label>Disabled</Label>
</MarkdownEditor>
<MarkdownEditor rows={1}>

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Der neue Test ist nicht sichtbar, da er nicht mehr in den viewport passt


await preview.click();

await testScreenshot("MarkdownEditor - preview");

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Der Test zeigt eine unerwünschte Veränderung

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

der Screenshot kann weg, dafür haben wir ja die Screenshot Tests

…bled state

ModeButton's internal Button unintentionally picked up the ambient
toolbarActionsPropsContext isDisabled meant for custom toolbar buttons,
disabling "Exit Preview" while in preview mode. Also split the new
custom-toolbar-button visual test case into its own screenshot so it
is not cropped by the fixed test viewport, and remove a stray vitest
failure-artifact screenshot that was committed by mistake.
@BenniEngel BenniEngel added the update-screenshots Label a PR to update the screenshots used for visual regression testing label Aug 10, 2026
@github-actions github-actions Bot removed the update-screenshots Label a PR to update the screenshots used for visual regression testing label Aug 10, 2026
github-actions Bot and others added 2 commits August 10, 2026 11:48
Co-authored-by: BenniEngel <187296787+BenniEngel@users.noreply.github.com>
@BenniEngel BenniEngel added the update-screenshots Label a PR to update the screenshots used for visual regression testing label Aug 10, 2026
@github-actions github-actions Bot removed the update-screenshots Label a PR to update the screenshots used for visual regression testing label Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Custom Buttons in MarkdownEditor

5 participants