Labels
Labels
344 labels
- Issues that impact the public API of the analyzer package
- Issues which have been reported due to an analysis server crash
- Use area-build for SDK build issues.
- SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries.
- Use area-dart-cli for issues related to the 'dart' command like tool.
- For issues related to conformance to the language spec in the parser, compilers or the CLI analyzer.
- Issues for the dart2wasm compiler.
- For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages.
- Prefer using 'type-documentation' and a specific area label.
- Tracking issues for internal work. Note that this area is not triaged.
- Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes.
- Tracking issues for the Dart IntelliJ plugin.
- Dart language related items (some items might be better tracked at github.com/dart-lang/language).
- Cross-cutting, high-level issues (for tracking many other implementation issues, ...).
- Deprecated: this label is no longer actively used (was: issues with the `dart migrate` tool).
- Used for native interop related issues, including FFI.
- Used for miscellaneous pkg/ packages not associated with specific area- teams.
- Deprecated: this label is no longer actively used.
- Use area-sdk for general purpose SDK issues (packaging, distribution, …).
- Deprecated: use area-language and a language- label.
- Cross-cutting test issues (use area- labels for specific failures; not used for package:test).
- A meta category for issues that should be addressed by tooling (prefer more concrete areas).
- Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.