Repository navigation
fix(markdown): recognize tab-separated code fence metadata - #36
Conversation
PR HealthPublish ✔️
Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation. This check can be disabled by tagging the PR with Changelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs. This check can be disabled by tagging the PR with Breaking changes ✔️
This check can be disabled by tagging the PR with API leaks ✔️The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.
This check can be disabled by tagging the PR with Unused Dependencies ✔️
For details on how to fix these, see dependency_validator. This check can be disabled by tagging the PR with License Headers ✔️
All source files should start with a license header. Unrelated files missing license headers
This check can be disabled by tagging the PR with Coverage ✔️
This check for test coverage is informational (issues shown here will not fail the PR). This check can be disabled by tagging the PR with |
ba1469d to
ac693c9
Compare
ac693c9 to
94a0b81
Compare
e6f1a70 to
71c6a82
Compare
Summary
```dart<TAB>line-numbers) producedclass="language-dart\tline-numbers"; now it yieldsclass="language-dart"anddata-metadata="line-numbers", matching cmark and commonmark.js.escapePunctuationwhen the input contains no backslash (~20x faster for that call; no measurable end-to-end change).test/fenced_code_info_test.dart,util_test.dart) and a CHANGELOG entry.Validation
dart format,dart analyze --fatal-infos,dart test(2829 passed). Differential vs main over spec inputs, 695 pub-cache READMEs/CHANGELOGs, Hebrew/CRLF samples and 80k fuzz cases: output identical except fence info strings containing a literal tab.