Moritz
Moritz
Fixes # > It's a good idea to open an issue first for discussion. - [ ] Tests pass - [ ] Appropriate changes to README are included in PR
Make the highlighting easier to parse visually, for example by highlighting comments, descritptions, `@@` keys etc. in different colors. The chosen colors should keep accessibility in mind.
To ease the maintenance of the dart-lang/ repositories, we are currently moving some of them into monorepos. Our thematically grouped monorepos are: - [build](https://github.com/dart-lang/build/) - [test](https://github.com/dart-lang/test/) - [native](https://github.com/dart-lang/native/) - [http](https://github.com/dart-lang/http/)...
- [ ] dart-lang/http2#124 - [ ] dart-lang/http#1377
Upgrade the pinned version, to help users avoid having to use dependency overrides. See also https://github.com/dart-lang/i18n/issues/914 ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process...
See https://github.com/dart-lang/tools/pull/1261 --- - [x] I’ve reviewed the contributor guide and applied the relevant portions to this PR. Contribution guidelines: - See our [contributor guide](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md) for general expectations for PRs....
Removing dynamic calls might be difficult because of the `Matcher` API, which heavily uses `dynamic`.
- Thanks for your contribution! Please replace this text with a description of what this PR is changing or adding and why, list any relevant issues, and review the contribution...