Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Enable Vue template indentation and content newline rules

Aperta
  • Qualcosa non va?
#9,145 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
78/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
eslint, javascript
Ambito
frontend, tooling

Direzione di ricerca

Start with eslint.config.mjs and remove only the three specified entries from libresign/disabled-during-migration. Run the provided layout-only preview on src/**/*.vue, then review the full diff before applying it and check for changes to rendered text or component behavior. Done means all three rules have no violations, formatting changes are limited to those rules, and the listed validation checks pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

frontend good first issue help wanted javascript technical debt

Goal

Enable three compatible Vue formatting rules together:

  • vue/html-indent
  • vue/singleline-html-element-content-newline
  • vue/multiline-html-element-content-newline

Enable these together: the newline autofix alone caused incorrect indentation in a previous trial. A combined, layout-only trial changed 34 Vue files and passed ESLint and git diff --check on main. Recheck on the latest revision.

Implementation steps

  1. Create a branch from the latest main.

  2. Remove only these three 'off' entries from libresign/disabled-during-migration in eslint.config.mjs. Keep the recommended Nextcloud severities.

  3. Preview the changes:

    npx eslint 'src/**/*.vue' \
  --fix-dry-run --fix-type layout --format json \
  > /tmp/eslint-preview.json

  4. Apply the changes:

    npx eslint 'src/**/*.vue' \
  --fix --fix-type layout

  5. Review the entire git diff, including opening/closing tags, nested content, component text, and indentation. Remove changes unrelated to the three rules.

  6. Submit one focused PR with valid DCO sign-offs.

Important constraints

This issue is formatting only. Do not change:

  • Vue component names, hierarchy, directives, or expressions.
  • Props, events, slots, IDs, CSS classes, or selectors.
  • Translation strings, visible text, or meaningful whitespace in rendered content.
  • JavaScript/TypeScript logic, assertions, test fixtures, or dependencies.

If a formatting change may affect rendered text or behavior, do not guess at a solution. Preserve behavior, add a suitable regression test if needed, and explain any remaining blocker in the PR.

Validation

git diff --check
npm run lint
npm run ts:check
npm run build

The Nextcloud preset treats the two newline rules as warnings. Also validate them at error severity only for this local check, without changing the project rule severities:

npx eslint 'src/**/*.vue' --plugin vue \
  --rule 'vue/singleline-html-element-content-newline: error' \
  --rule 'vue/multiline-html-element-content-newline: error'

Run focused Vitest tests for affected components. For materially visible changes, provide a screenshot or short recording of the relevant UI, without sensitive data.

Acceptance criteria

  • All three rules are enabled together, preserving Nextcloud's recommended severities.
  • No violations of any of the three rules remain, including warning-level ones.
  • Vue indentation is consistent and git diff --check passes.
  • No intended rendered text, accessibility markup, events, slots, or behavior changes.
  • Relevant component tests and the required checks pass.
  • One focused PR resolves this issue with valid DCO.

Good first issue

This is a guided Vue/ESLint task with a known set of commands and boundaries. No component redesign or new tooling is expected.

Interested contributors may comment for guidance or scope confirmation. Prior approval is not required for a valid contribution.

Additional context

Community support: https://t.me/LibreSign

Lingua principale
PHP
Stelle
835
Fork
167
Merge medio
17h 1m
PR unite (30g)
477

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LibreSign/libresign

Tutte le issue di LibreSign/libresign

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.