Add option to skip some code blocks
See original GitHub issuedocusaurus-preset-shiki-twoslash
is incompatible with Docusaurus’s live code blocks, since it gobbles up all of the code blocks. I only want Shiki/Twoslash on some of my code blocks, while others I want to be interactive code playgrounds.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Where could I add option to disable auto compiler detection?
Where could I add option to disable auto compiler detection? I am thinking a check box that defaults to checked in. Setting ->...
Read more >Option to ignore code blocks (.js) or individual links in .html ...
I've been implementing PWA features in my app and I've encountered a few roadblocks... 1.) All the icons in my .webmanifest and head...
Read more >How can I skip some block content while reading in Perl
Perl already has an operator to keep track of blocks. It's called the "flip-flop" operator: Try this out: while ( <DATA> ) {...
Read more >Skip to main content - IT Accessibility - NC State University
Having a skip to main content link appear when it receives keyboard focus. The text is hidden offscreen in a manner that allows...
Read more >Code blocks - Squarespace Help Center
Use code blocks to add custom code to a page, blog post, sidebar, footer, or other content area. Code blocks are good options...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh yes, thanks for the issue. I’m pretty confident docusaurus will handle the rest if we could just pass the props correctly to it. In this case,
jsx live
requires that we need to pass thelive
prop to the docusaurus which we currently don’t.To prevent further incidents, we should just pass the parsed meta keys whether important or not. It’ll make things much easier. In worst scenario, the user might need to write a line or two to override/swizzle our
MDXComponents
file.I personally think the current implementation of the
parseCodeInfo
is kinda sphegatti. I’ll open a PR soon with a fix for this.I want to know how to solve it