Audit the remaining deferred ESLint rules and document justified exceptions
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
- 8/100
- Tipo de issue
- Refactorización
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- eslint, javascript
- Área
- developer-experience
Línea de trabajo
Start with the effective rule configuration in eslint.config.mjs and the .editorconfig tab convention, then check the cited files src/components/PdfEditor/Signature.vue and src/views/Settings/ConfigureCheck.vue, where v-html renders row.message. Done means one decision record per rule (enable, defer with a dependency, or intentionally disable with a justification) backed by a fresh lint inventory on the base SHA, plus a review of #9498-#9502 and PR #9497 on main. This needs maintainer policy decisions, so it is not a first-timer task.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Goal
Make an evidence-based, maintainable decision about the 16 remaining deferred ESLint rules not covered by #9498-#9502. This is a technical classification and final handoff, not a mass-refactor task.
Rules in scope
- Translations:
@nextcloud/l10n-enforce-ellipsis,@nextcloud/l10n-non-breaking-space. - Vue/API contracts:
vue/attribute-hyphenation,vue/custom-event-name-casing,vue/slot-name-casing,vue/v-on-event-hyphenation,vue/no-v-html,vue/multi-word-component-names,camelcase. - Indentation:
@stylistic/indent,@stylistic/no-tabs. - Documentation:
jsdoc/require-jsdoc,jsdoc/require-param,jsdoc/require-param-description. - Other:
antfu/top-level-function,vue/no-unused-properties.
Evidence to collect
- Capture base SHA and a fresh current lint inventory for every rule; include effective preset options and affected files. Existing
eslint.config.mjshit counts are historical. - Classify each rule as enable now, defer with a stated dependency, or intentionally disabled with a technical justification. Record evidence, tradeoffs, affected contracts, test strategy and accountable maintainer decision.
- Verify examples before deciding:
.editorconfigrequires tabs, so@stylistic/no-tabsconflicts with the current project convention;src/components/PdfEditor/Signature.vueemitsonUpdate/onDelete;src/views/Settings/ConfigureCheck.vueusesv-htmlonrow.message; the policy catalog uses HTML highlighting with explicit escaping. Do not assume these all have the same risk or that changing names is harmless. - Avoid dummy JSDoc comments and cosmetic renames of Vue events, slots or backend/API field names. Treat translation strings and generated artifacts as protected boundaries.
- Review the final implementation results of #9498-#9502 and PR #9497 against the actual integrated
main, including lint/type/build/test checks; do not infer success from closed issue counts. - If the audit finds further independent implementation deliverables, propose them for separate approval rather than quietly expanding the task or closing the epic prematurely. Report security-sensitive HTML findings through the appropriate private disclosure process when needed.
Deliverable / acceptance criteria
- One per-rule decision record for all 16 rules, with current measured evidence and relevant contracts.
- Decisions are explicitly reviewed for Vue/API/translation/security impacts; unresolved decisions are not labeled complete.
- Justified intentional disables have concise, non-stale explanations near the effective configuration.
- Integrated checks on
mainhave been verified or report the exact blocker. - The epic's final acceptance criteria can be judged without relying solely on a 100% sub-issue counter.
Out of scope and contributor suitability
Do not mass-change runtime code, Vue event names, API fields, translations or indentation while producing this audit. The work requires policy and architecture decisions; keep it available for maintainers/experienced contributors, not good first issue.
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 help wanted javascript technical debt
Dificultad 4/5 3-5 días Aptitud para principiantes 25/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