biomejs
biome
Blog
Docs
Changelog
Blog
Docs
Changelog
Overview
Branches
Benchmarks
Runs
Performance History
Latest Results
fix(markdown_parser): diagnose backtick in fence info string Per CommonMark §4.5, the info string after a backtick fence cannot contain backticks. The parser already rejects such input as a fenced code block, but did so silently. This adds a diagnostic so users understand why their intended code block is rendered as paragraph text. The parsed AST/CST is unchanged. Tilde fences continue to accept backticks in info strings per spec. - New parse_error::info_string_contains_backtick diagnostic. - New fenced_code_block::backtick_info_violation token-level lookahead helper returning the TextRange of the offending backtick. - Emit from parse_any_block_with_indent_code_policy and from handle_line_continuation (covers both fresh-block and paragraph-continuation paths). - Move tests/md_test_suite/ok/fenced_code_info_backtick.md to error/. - Add tests/md_test_suite/ok/tilde_fence_info_backtick.md positive control proving tilde fences are unaffected. - Update three biome_markdown_formatter prettier snapshots to include the new diagnostic in their # Errors block (formatted output unchanged).
jfmcdowell:fix/md-info-string-backtick
42 minutes ago
test(markdown_formatter): update prettier snapshots for new info-string diagnostic
jfmcdowell:fix/md-info-string-backtick
51 minutes ago
fix(markdown_parser): diagnose backtick in fence info string Per CommonMark §4.5, the info string after a backtick fence cannot contain backticks. The parser already rejects such input as a fenced code block, but did so silently. This adds a diagnostic so users understand why their intended code block is rendered as paragraph text. The parsed AST/CST is unchanged. Tilde fences continue to accept backticks in info strings per spec. - New parse_error::info_string_contains_backtick diagnostic. - New fenced_code_block::backtick_info_violation token-level lookahead helper returning the TextRange of the offending backtick. - Emit from parse_any_block_with_indent_code_policy and from handle_line_continuation (covers both fresh-block and paragraph-continuation paths). - Move tests/md_test_suite/ok/fenced_code_info_backtick.md to error/. - Add tests/md_test_suite/ok/tilde_fence_info_backtick.md positive control proving tilde fences are unaffected. - Update three biome_markdown_formatter prettier snapshots to include the new diagnostic in their # Errors block (formatted output unchanged).
jfmcdowell:fix/md-info-string-backtick
51 minutes ago
[autofix.ci] apply automated fixes
theBGuy:fix/use-anchor-content-render-prop
3 hours ago
[autofix.ci] apply automated fixes
dyc3/simd-line-index
4 hours ago
refactor(line_index): use SIMD intrinsics for better performance
dyc3/simd-line-index
5 hours ago
refactor(line_index): use SIMD intrinsics for better performance
dyc3/simd-line-index
5 hours ago
feat(lint/html/vue): add `noVueVOnNumberValues`
dyc3/noVueVOnNumberValues
7 hours ago
Latest Branches
CodSpeed Performance Gauge
-1%
fix(markdown_parser): diagnose backtick in fence info string
#10224
58 minutes ago
d8e6367
jfmcdowell:fix/md-info-string-backtick
CodSpeed Performance Gauge
0%
fix(a11y/useAnchorContent): don't flag <a> elements used as render props
#10220
4 hours ago
6266f0c
theBGuy:fix/use-anchor-content-render-prop
CodSpeed Performance Gauge
0%
refactor(line_index): use SIMD intrinsics for better performance
#10221
4 hours ago
f87cbf0
dyc3/simd-line-index
© 2026 CodSpeed Technology
Home
Terms
Privacy
Docs