master - external/github.com/dart-lang/markdown

commit	782b1803a29aa964410d93b4437d5d1efa47f6b4	[log] [tgz]
author	dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	Mon Apr 01 02:50:21 2024
committer	GitHub <noreply@github.com>	Mon Apr 01 02:50:21 2024
tree	0e09c6f9cc9f17e4164bee0fb4ef9ac0acc77fc4
parent	8a480f3f05dd29534d01df4b7fb20c5de1eda188 [diff]

Bump subosito/flutter-action from 2.12.0 to 2.15.0 (#603)

Bumps [subosito/flutter-action](https://github.com/subosito/flutter-action) from 2.12.0 to 2.15.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/subosito/flutter-action/releases">subosito/flutter-action's releases</a>.</em></p>
<blockquote>
<h2>v2.15.0</h2>
<p>Hi! I'm <a href="https://github.com/bartekpacia/">Bartek</a> and I'm a new maintainer of this action. I promise to take good care of it.</p>
<p>This release introduces the <code>flutter-version-file</code> option, which lets you easily centralize Flutter version in a single place â your pubspec.yaml file:</p>
<p>You can use it like this:</p>
<pre lang="yaml"><code>steps:
  - name: Clone repository
    uses: actions/checkout@v4
  - name: Set up Flutter
    uses: subosito/flutter-action@v2
    with:
      channel: stable
      flutter-version-file: pubspec.yaml # path to pubspec.yaml
</code></pre>
<p>Please note that for this to work, you need to specify exact Flutter version in pubspec.yaml:</p>
<pre lang="yaml"><code>environment:
  dart: &quot;&gt;=3.3.0 &lt;4.0.0&quot;
  flutter: 3.19.0 # This must be exact! No ranges allowed.
</code></pre>
<p>Apart from that, some minor README updates and code cleanup were performed.</p>
<h2>v2.14.0</h2>
<p>No release notes provided.</p>
<h2>v2.13.0</h2>
<p>No release notes provided.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/subosito/flutter-action/commit/3d804929922b667a63a229bc59037807f969e885"><code>3d80492</code></a> update README (<a href="https://redirect.github.com/subosito/flutter-action/issues/291">#291</a>)</li>
<li><a href="https://github.com/subosito/flutter-action/commit/0ef13f12a53071c2362b0f884ad917692ff8cbc5"><code>0ef13f1</code></a> Add <code>flutter-version-file</code> (<a href="https://redirect.github.com/subosito/flutter-action/issues/290">#290</a>)</li>
<li><a href="https://github.com/subosito/flutter-action/commit/7564de34b3630708aa08807092c5ddbf4f6e0a7d"><code>7564de3</code></a> Merge pull request <a href="https://redirect.github.com/subosito/flutter-action/issues/288">#288</a> from subosito/chore/action_yaml_refactor</li>
<li><a href="https://github.com/subosito/flutter-action/commit/2b3ab6c7da1a24f4e4589856c0609a28c2393e7c"><code>2b3ab6c</code></a> convert some if-statements to be POSIX-compatible</li>
<li><a href="https://github.com/subosito/flutter-action/commit/49cd17165c0e40bec4f918edd05e5e1e5e1938c9"><code>49cd171</code></a> split longer lines</li>
<li><a href="https://github.com/subosito/flutter-action/commit/cf12a399890e96433bcc3bcd58cf894cb9f36162"><code>cf12a39</code></a> Merge pull request <a href="https://redirect.github.com/subosito/flutter-action/issues/287">#287</a> from subosito/minor</li>
<li><a href="https://github.com/subosito/flutter-action/commit/cea4cf68a127f658cd53308d618402e7e0bc4e52"><code>cea4cf6</code></a> workflow.yaml: minor fix</li>
<li><a href="https://github.com/subosito/flutter-action/commit/043862d93028d14cac42b28d5eecbc99aaef64f4"><code>043862d</code></a> Merge pull request <a href="https://redirect.github.com/subosito/flutter-action/issues/286">#286</a> from subosito/format</li>
<li><a href="https://github.com/subosito/flutter-action/commit/e70699e140cf8f07d411bafa936437de5a7560e1"><code>e70699e</code></a> file renames</li>
<li><a href="https://github.com/subosito/flutter-action/commit/766e0c11bc704f670072f0bb23cd50d33e7be3cd"><code>766e0c1</code></a> minor readme format update</li>
<li>Additional commits viewable in <a href="https://github.com/subosito/flutter-action/compare/2783a3f08e1baf891508463f8c6653c258246225...3d804929922b667a63a229bc59037807f969e885">compare view</a></li>
</ul>
</details>
<br />

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=subosito/flutter-action&package-manager=github_actions&previous-version=2.12.0&new-version=2.15.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

.github/workflows/flutter_markdown.yaml[diff]

1 file changed

tree: 0e09c6f9cc9f17e4164bee0fb4ef9ac0acc77fc4

README.md

A portable Markdown library written in Dart. It can parse Markdown into HTML on both the client and server.

Play with it at dart-lang.github.io/markdown.

Usage

import 'package:markdown/markdown.dart';

void main() {
  print(markdownToHtml('Hello *Markdown*'));
  //=> <p>Hello <em>Markdown</em></p>
}

Syntax extensions

A few Markdown extensions, beyond what was specified in the original Perl Markdown implementation, are supported. By default, the ones supported in CommonMark are enabled. Any individual extension can be enabled by specifying an Array of extension syntaxes in the blockSyntaxes or inlineSyntaxes argument of markdownToHtml.

The currently supported inline extension syntaxes are:

InlineHtmlSyntax() - approximately CommonMark's definition of “Raw HTML”.

The currently supported block extension syntaxes are:

const FencedCodeBlockSyntax() - Code blocks familiar to Pandoc and PHP Markdown Extra users.
const HeaderWithIdSyntax() - ATX-style headers have generated IDs, for link anchors (akin to Pandoc's auto_identifiers).
const SetextHeaderWithIdSyntax() - Setext-style headers have generated IDs for link anchors (akin to Pandoc's auto_identifiers).
const TableSyntax() - Table syntax familiar to GitHub, PHP Markdown Extra, and Pandoc users.

For example:

import 'package:markdown/markdown.dart';

void main() {
  print(markdownToHtml('Hello <span class="green">Markdown</span>',
      inlineSyntaxes: [InlineHtmlSyntax()]));
  //=> <p>Hello <span class="green">Markdown</span></p>
}

Extension sets

To make extension management easy, you can also just specify an extension set. Both markdownToHtml() and Document() accept an extensionSet named parameter. Currently, there are four pre-defined extension sets:

ExtensionSet.none includes no extensions. With no extensions, Markdown documents will be parsed with a default set of block and inline syntax parsers that closely match how the document might be parsed by the original Perl Markdown implementation.
ExtensionSet.commonMark includes two extensions in addition to the default parsers to bring the parsed output closer to the CommonMark specification:
- Block Syntax Parser
  - const FencedCodeBlockSyntax()
- Inline Syntax Parser
  - InlineHtmlSyntax()
ExtensionSet.gitHubFlavored includes five extensions in addition to the default parsers to bring the parsed output close to the GitHub Flavored Markdown specification:
- Block Syntax Parser
  - const FencedCodeBlockSyntax()
  - const TableSyntax()
- Inline Syntax Parser
  - InlineHtmlSyntax()
  - StrikethroughSyntax()
  - AutolinkExtensionSyntax()
ExtensionSet.gitHubWeb includes eight extensions. The same set of parsers use in the gitHubFlavored extension set with the addition of the block syntax parsers, HeaderWithIdSyntax and SetextHeaderWithIdSyntax, which add id attributes to headers and inline syntax parser, EmojiSyntax, for parsing GitHub style emoji characters:
- Block Syntax Parser
  - const FencedCodeBlockSyntax()
  - const HeaderWithIdSyntax(), which adds id attributes to ATX-style headers, for easy intra-document linking.
  - const SetextHeaderWithIdSyntax(), which adds id attributes to Setext-style headers, for easy intra-document linking.
  - const TableSyntax()
- Inline Syntax Parser
  - InlineHtmlSyntax()
  - StrikethroughSyntax()
  - EmojiSyntax()
  - AutolinkExtensionSyntax()

Custom syntax extensions

You can create and use your own syntaxes.

import 'package:markdown/markdown.dart';

void main() {
  var syntaxes = [TextSyntax('nyan', sub: '~=[,,_,,]:3')];
  print(markdownToHtml('nyan', inlineSyntaxes: syntaxes));
  //=> <p>~=[,,_,,]:3</p>
}

HTML sanitization

This package offers no features in the way of HTML sanitization. Read Estevão Soares dos Santos's great article, “Markdown's XSS Vulnerability (and how to mitigate it)”, to learn more.

The authors recommend that you perform any necessary sanitization on the resulting HTML, for example via dart:html's NodeValidator.

CommonMark compliance

This package contains a number of files in the tool directory for tracking compliance with CommonMark.

Updating CommonMark stats when changing the implementation

Update the library and test code, making sure that tests still pass.
Run dart run tool/stats.dart --update-files to update the per-test results tool/common_mark_stats.json and the test summary tool/common_mark_stats.txt.
Verify that more tests now pass – or at least, no more tests fail.
Make sure you include the updated stats files in your commit.

Updating the CommonMark test file for a spec update

Check out the CommonMark source. Make sure you checkout a major release.

Dump the test output overwriting the existing tests file.

> cd /path/to/common_mark_dir
> python3 test/spec_tests.py --dump-tests > \
  /path/to/markdown.dart/tool/common_mark_tests.json

Update the stats files as described above. Note any changes in the results.
Update any references to the existing spec by search for https://spec.commonmark.org/0.30/ in the repository. (Including this one.) Verify the updated links are still valid.
Commit changes, including a corresponding note in CHANGELOG.md.