Feature Request: ability to suppress certain warnings

[DartBot]

This issue was originally filed by ross.dart.lan...@gmail.com

---

It would be quite useful if all warnings in the spec were to be uniquely numbered.

1. This would make it easier for looking up observed warnings in the spec for detailed explanation.

2. These identifiers could be used in metadata, command line arguments, build scripts, etc... to suppress warnings.

This allows the analyzer and other tools to be fully spec-compliant, while providing an 'out' to developers who want warning-free code and may not have any means to work around them (or the cost of working around them is too costly).

thanks,

[sethladd]

I think there is some discussion around a way to opt-out of certain warnings. Maybe through a metadata annotation? Adding a few folks who might know where the discussion is.

Also, changing the title of this to be more specific (hope that's OK)

---

cc @gbracha.
cc @bwilkerson.
Removed Type-Defect label.
Added Type-Enhancement, Area-Editor, Triaged labels.
Changed the title to: "Feature Request: ability to suppress certain warnings".

[gbracha]

Changed the area to language. This is not an editor issue; for example, dart2js needs to treat any annotations regarding suppression in the same way. In fact, any Dart implementation does. Otherwise there is little point n putting such annotations in the source; if it were tool specific, it could be indicated interactively, or in a settings file etc.

---

cc @peter-ahe-google.
cc @lukechurch.
Set owner to @gbracha.
Removed Area-Editor label.
Added Area-Language, Accepted labels.

[pq]

Curious if there's been any progress on this one.

We're considering the more modest proposal of adding a way to suppress lints in the linter via comment conventions (#57193). If we could do it with a bonafide annotation, all the better!

[DartBot]

This comment was originally written by ir...@google.com

---

C1

Can we increase the priority of this bug? Ideally we want to be able to treat warnings as errors but cannot do that since some warnings and hints are not real warnings or hints. Ex: an attribute that is called from generated code (ex: angular template).

@SuppressWarning(type of warnings, "reason") on a class member or method or class.

[sethladd]

Added C1 label.