Skip to content

literal_only_boolean_expressions tests should include literal bools in when #59057

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
srawlins opened this issue Mar 9, 2023 · 0 comments · Fixed by dart-archive/linter#4178
Assignees
Labels
devexp-linter Issues with the analyzer's support for the linter package legacy-area-analyzer Use area-devexp instead. linter-false-negative linter-new-language-feature P2 A bug or feature request we're likely to work on
Milestone

Comments

@srawlins
Copy link
Member

srawlins commented Mar 9, 2023

Child issue of #58837

For example:

switch (obj) {
  case [int a, int n] when true: // LINT
  case {"a": int a}:
    print(a.abs());
}
@pq pq self-assigned this Mar 9, 2023
@pq pq added this to the Dart 3 beta 3 milestone Mar 13, 2023
@pq pq removed their assignment Mar 20, 2023
@pq pq added P2 A bug or feature request we're likely to work on linter-false-negative labels Mar 20, 2023
@pq pq self-assigned this Mar 20, 2023
@devoncarew devoncarew added devexp-linter Issues with the analyzer's support for the linter package legacy-area-analyzer Use area-devexp instead. labels Nov 19, 2024
@devoncarew devoncarew transferred this issue from dart-archive/linter Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devexp-linter Issues with the analyzer's support for the linter package legacy-area-analyzer Use area-devexp instead. linter-false-negative linter-new-language-feature P2 A bug or feature request we're likely to work on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants