Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add invalid_runtime_check_with_js_interop_types, unintended_html_in_d…
…oc_comment (#285) - add `invalid_runtime_check_with_js_interop_types` - add `unintended_html_in_doc_comment` - prep for publishing The idea behind this revision is to use the above two lints for a period of time ourselves (these lints are likely going out with the next major revision of `package:lints` - see https://github.com/orgs/dart-lang/projects/73). --- - [x] I’ve reviewed the contributor guide and applied the relevant portions to this PR. <details> <summary>Contribution guidelines:</summary><br> - See our [contributor guide](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md) for general expectations for PRs. - Larger or significant changes should be discussed in an issue before creating a PR. - Contributions to our repos should follow the [Dart style guide](https://dart.dev/guides/language/effective-dart) and use `dart format`. - Most changes should add an entry to the changelog and may need to [rev the pubspec package version](https://github.com/dart-lang/sdk/blob/main/docs/External-Package-Maintenance.md#making-a-change). - Changes to packages require [corresponding tests](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md#Testing). Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback. </details>
- Loading branch information