Repository navigation
refactor(markdown): apply upstream review suggestions for footnotes and plain-text syntax - #42
Conversation
…nd plain-text syntax #42
a5525d7 to
7854b90
Compare
PR HealthPublish ✔️
Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation. 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
|
| File | Coverage |
|---|---|
| pkgs/markdown/lib/src/document.dart | 💔 96 % ⬇️ 0 % |
| pkgs/markdown/lib/src/inline_parser.dart | 💚 99 % ⬆️ 0 % |
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 skip-coverage-check.
Applies the gemini-code-assist suggestions accepted on the upstream PRs, so
mainstays equal to the union of the topic branches:_footnoteLabelIndexinstead of rebuilding an ordinal map._PlainTextSyntaxper configuration (no RegExp compile perInlineParser), and look up built-in inline syntaxes in a staticSet.No behavior change. format / analyze --fatal-infos / test (2856 passed) clean locally.