Enable type safety, unused-symbol and definition-order lint rules
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Refactorización
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- eslint, javascript, typescript
- Área
- devtools
Línea de trabajo
Start with eslint.config.mjs, including the generated OpenAPI override, to see which core and TypeScript rules already apply to .js, .ts and .vue files. Enable one of the five listed rules on a branch from main, then run npm run lint to record the real violations and the files they affect before changing anything. Done means each rule is enabled on its intended file types, its violations are fixed without weakening tests, and npm run lint, npm run ts:check, npm test and npm run build pass.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Goal
Review and enable five deferred semantic JavaScript/TypeScript rules, fixing real problems rather than changing logic to make lint quiet.
Rules
@typescript-eslint/no-explicit-any(~17 historical hits)@typescript-eslint/no-unused-vars(~78)@typescript-eslint/no-use-before-define(~38)no-unused-vars(~3)no-use-before-define(~8)
The sum (~144) may overlap; recalculate on current main.
Getting started
- Read
eslint.config.mjs, including the generated OpenAPI override. Establish which core rules and which TypeScript extension rules should apply to.js,.tsand.vuefiles. Do not activate conflicting duplicate diagnostics. - Enable one rule at a time in a branch from
main. Record real violations, affected files and why the flag exists before applying any fix. - When addressing
any, prefer a concrete type orunknownplus verified narrowing, not a permissive cast that hides the original issue. - Before deleting an apparently unused symbol, check callers, module exports, initialization-time behavior and test fixtures. Before moving a declaration, check when it is initialized and executed.
- Keep per-rule DCO-signed commits and document any narrowly justified exceptions. Do not weaken tests or use blanket suppressions.
Tests and evidence
Run git diff --check, npm run lint, npm run ts:check, npm test and npm run build. For changed public exports, tests or initialization order, add focused regression tests that would fail if the behavior changed. Include the effective rule matrix by file type in the PR review description.
Done when
- Rules run on the intended file types without duplicate false positives.
- Types are meaningful; no legitimate side effects, consumers or public contracts are removed.
- Tests and CI pass, or precise blockers are recorded for maintainer decisions.
- Changes remain narrowly scoped and traceable per rule.
Out of scope and contributor suitability
Do not change generated API types, JSDoc policy or Vue public-property rules. This requires semantic inspection and is not a good first issue in its present combined scope.
Additional context
Development workflow: https://docs.libresign.coop/developer_manual/development-workflow.html
Questions: https://t.me/LibreSign
- Lenguaje dominante
- PHP
- Estrellas
- 844
- Forks
- 176
- Merge medio
- 14 h 3 min
- PR fusionados (30 d)
- 344
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de LibreSign/libresign
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
OpenSSL engine: leaf certificates get O=Internet Widgits Pty Ltd, ST=Some-State from system openssl.cnfPosiblemente ocupada @vitormattos la tomó hace 5 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
LibreSign/libresign#9366 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 83/100
LibreSign/libresign#9007 · 2 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
LibreSign/libresign#8284 · 5 comentarios ·
Los mantenedores suelen responder en 1 día
-
frontend javascript technical debt
Dificultad 5/5 Más de una semana Aptitud para principiantes 8/100
Los mantenedores suelen responder en 1 día
Todos los issues de LibreSign/libresign
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
Automattic/blocks-engine#6318 ·
Los mantenedores suelen responder en 1 día
-
kind/enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
[remove-resource] Delete Open Course Hub, Open Multicourse Hub, and Learn2 with GitSync skeletonsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
Allow @ in the service nameAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100