Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

dart-run-static-analysis: plugin guidance describes the legacy plugin system, and the example includes a file that doesn't exist

Aberta Para iniciantes
#244 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
90/100
Tipo de issue
Documentação
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
dart
Domínio
documentation

Direção de pesquisa

Comece por skills/dart-run-static-analysis/SKILL.md e compare as orientações sobre plugins com a documentação moderna de plugins do servidor de análise vinculada na issue. Atualize o exemplo e as explicações para plugins modernos e legacy, a ativação de lint, a reinicialização do servidor, o include válido de flutter_lints e a remoção de missing_return. Aplique o fix upstream em dart-lang/skills e, em seguida, verifique as orientações sincronizadas neste repositório.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Skill: skills/dart-run-static-analysis/SKILL.md, unchanged on main since fbb6bbc.

Found these while setting up a new-style analyzer plugin.

1. Plugin setup uses the legacy config

The skill says to put plugins under analyzer: plugins: and add them as dev dependencies. That's the legacy setup, not the setup for the modern plugin system introduced in Dart 3.10 / Flutter 3.38.

For modern plugins, use a top-level plugins: section. The analysis server resolves plugin dependencies separately, so adding the plugin to the project's pubspec.yaml isn't needed just to enable it.

The skill also leaves out that plugin warnings are on by default, but lint rules are off unless enabled under the plugin's diagnostics: key, directly or through an included options file.

Example, with placeholder package and rule names:

plugins:
  my_plugin:
    version: ^1.0.0
    diagnostics:
      rule_1: true
      rule_2: false

Please update the guidance to distinguish modern and legacy plugins, include lint activation, and mention restarting the analysis server after changing plugins:. The current instructions don't enable a modern-only plugin through the modern loader.

2. The example's include path doesn't exist

include: package:flutter_lints/recommended.yaml

flutter_lints 6.0.0 ships lib/flutter.yaml, not lib/recommended.yaml. Use the documented include:

include: package:flutter_lints/flutter.yaml

For pure Dart, use package:lints/recommended.yaml. This also matches the skill's own Base Configuration bullet.

3. missing_return is obsolete

The example sets missing_return: error. The analyzer lists MISSING_RETURN among its removed diagnostic codes. It's still accepted for compatibility, but the override no longer does anything. Please remove it from the example.

Environment

  • Model: Claude Opus 5.5.
  • Harness: Claude Code, with a plugin that vendors these skills.
  • Dart/Flutter SDK: Dart 3.13.4, Flutter 3.47.5.

The same file exists in dart-lang/skills, which syncs into this repository, so the fix needs to happen upstream.

Linguagem predominante
Dart
Estrelas
3.1k
Forks
183
Merge médio
4d 10h
PRs com merge (30d)
6

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de flutter/agent-plugins

Todas as issues de flutter/agent-plugins

Issues semelhantes

Mais issues de Dart

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.