docs: fix broken code block formatting in @unkey/cache overview#6238
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: fix broken code block formatting in @unkey/cache overview#6238mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Repair the corrupted "Hello World" code sample in
libraries/ts/cache/overview.mdxso the example renders as TypeScript again instead of leaking into prose.Changes
```ts Hello Worldfence out of the indented<CodeGroup>block so the fence is recognized at the document level./** ... */JSDoc comments that had been mangled into escaped Markdown lists (/\*\*,- Define ...,\*/).createCache({ ... })object literal that had collapsed to column 0.(4-backtick) closing fence with a normal``` ```` closing fence.});→}),inside thecreateCacheobject literal) introduced by the same earlier reformatting.Context
A previous "writing style standardization" pass reformatted this file and broke the first code block, causing the page to render the sample as escaped prose rather than code. A full-docs scan turned up no other spelling, grammar, duplicate-word, frontmatter, or markdown-syntax issues.