Skip to content

Commit

Permalink
[wildcard-variables] Add 'no_wildcard_variable_uses' lint to breaking…
Browse files Browse the repository at this point in the history
… change section. (#3785)
  • Loading branch information
kallentu committed May 9, 2024
1 parent a1bf79d commit ff28cb6
Showing 1 changed file with 11 additions and 1 deletion.
12 changes: 11 additions & 1 deletion working/wildcards/feature-specification.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Author: Bob Nystrom

Status: In-progress

Version 1.1
Version 1.2

Pattern matching brings a new way to declare variables. Inside patterns, any
variable whose name is `_` is considered a "wildcard". It behaves like a
Expand Down Expand Up @@ -395,8 +395,18 @@ However, this *is* a breaking change. If this ships in the same version as
pattern matching, we can gate it behind a language version and only break code
when it upgrades to that version.

### Existing Lints

We have an existing [`no_wildcard_variable_uses`](https://dart.dev/tools/linter-rules/no_wildcard_variable_uses) lint, which advises users to avoid using wildcard parameters or variables.

This lint is included in the core lint set which means that the scale of the breaking change should be small since most projects should have this lint enabled.

## Changelog

### 1.2

- Add information about the [`no_wildcard_variable_uses`](https://dart.dev/tools/linter-rules/no_wildcard_variable_uses) lint.

### 1.1

- Add rules about `super._` and about extension types.
Expand Down

0 comments on commit ff28cb6

Please sign in to comment.