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

Engine messages hard-code CLI flag names; give them structured codes instead

Cerrado
  • ¿Algo no está bien?
#100 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
backend-api-design, cli

Línea de trabajo

Start by reading the message strings in internal/scan/runner.go, options.go, scope.go, verdict.go, internal/dns/resolver.go and transport.go, then inspect the rewrite tables in pkg/subenum/subenum.go and their tests. The issue allows either structured codes and settings or neutral setting names, but replacing message parsing across engine and front ends is broad design work. Done means no engine message hard-codes CLI flags and the CLI, TUI and pkg/subenum each present settings in their own terms without parsing message text.

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

Descripción

area: scan enhancement

Why it matters

Engine messages name command-line flags ("Use -force to scan anyway", "set -max-queries or -force", "concurrency (-t) must be at least 1"). That reads well in the CLI but is wrong anywhere else: the TUI has form fields, and pkg/subenum callers have Config fields, not flags.

Evidence

  • About 40 flag references in message strings across internal/scan/runner.go, options.go, scope.go, verdict.go and internal/dns/resolver.go, transport.go.
  • pkg/subenum works around this with a regexp that rewrites -flag to the matching Config field (flagFields and fieldNames in pkg/subenum/subenum.go). It works and is tested, but a new message that names a flag missing from the table gets through unchanged.

Suggested approach

  • Give events and validation errors a structured part: a code such as wildcard_refused or cap_reached, and the setting involved (force, max_queries). Each front end then writes its own wording.
  • Or, as a smaller step, have the engine refer to settings by neutral names and let each front end map them.
  • Delete the regexp rewrite in pkg/subenum once the engine no longer writes flag names.

Done when

No engine message hard-codes a CLI flag, and the CLI, the TUI and pkg/subenum each name settings in their own terms without parsing message text.

Lenguaje dominante
Go
Estrellas
1
Forks
1
Merge medio
5 d 2 h
PR fusionados (30 d)
3

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 TMHSDigital/subenum

Todos los issues de TMHSDigital/subenum

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.