Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto Apto para principiantes
  • ¿Algo no está bien?
#244 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
90/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
dart
Área
documentation

Línea de trabajo

Comienza con skills/dart-run-static-analysis/SKILL.md y compara sus indicaciones sobre plugins con la documentación moderna de plugins del servidor de análisis enlazada en el issue. Actualiza el ejemplo y las explicaciones para plugins modernos y legacy, la activación de lint, el reinicio del servidor, el include válido de flutter_lints y la eliminación de missing_return. Aplica el fix upstream en dart-lang/skills y, después, verifica las indicaciones sincronizadas en este repositorio.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Dart
Estrellas
3k
Forks
182
Merge medio
2 d 19 h
PR fusionados (30 d)
6

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de flutter/agent-plugins

Todos los issues de flutter/agent-plugins

Issues similares

Más issues de Dart

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.