Add fullscreen controls to Mermaid diagrams - #16
Draft
davidmoshal wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #14, which shipped Mermaid rendering in v0.9.0. This clean PR supersedes #15, whose branch was mistakenly force-pushed after the original rendering work became redundant.
Summary
Validation
pnpm build:webpnpm test:web(8/8)pnpm test:clipnpm build:clipnpm test:racepnpm test:browser(8/8)openknowledge validate WikiNo dependency or lockfile changes are included.
Local tooling note
The aggregate
pnpm testwrapper reached the unchanged packed-npm smoke test, where pnpm 10.33 propagated a project-scopedallow-scriptssetting that npm 11.19 rejects. Running the unchanged test directly withnode scripts/test-packed-npm.mjspassed.