Support for @deprecated annotations (as structured doc comments) #3753
Labels
area-analyzer
Use area-analyzer for Dart analyzer issues, including the analysis server and code completion.
type-enhancement
A request for a change that isn't a bug
Milestone
This follows-up on basic support required for dartbug.com/3752.
In short, references to deprecated elements (functions, fields, types) should get a warning marker (and possibly a strikethrough semantic highlighting).
As a first cut, we will use the following simple format:
// @deprecated
and insist that it be on a line immediately preceding a member declaration. For example:
// @deprecated
interface TimeZone default TimeZoneImplementation
As for scope, we want to at least be able to flag members (fields, methods) and this is certainly a reasonable starting point. Statement-level scope is more contentious but very much on the table.
The text was updated successfully, but these errors were encountered: