robinp2000/dachshund-auth-provider
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore: add ESLint with angular-eslint to the frontend #23

Merged
robinp2000 merged 1 commit from robinp2000/chore/frontend-eslint into main 2026-10-18 16:19:07 +02:00 AGit
Conversation 0 Commits 1 Files changed 4 +1967 -66
robinp2000 commented 2026-10-18 16:15:11 +02:00
Owner
Copy link

What

  • Add ESLint 10 with angular-eslint 21, typescript-eslint and the default
    Angular rule sets (ng add angular-eslint@21), including the lint npm
    script and the lint target in angular.json.
  • Do not enforce a selector prefix: the components use mixed prefixes (app-,
    component-, none), so prefix is an empty array in both selector rules.
    The selector style (kebab-case / camelCase) is still checked.

Why

Prettier only covers formatting. ESLint finds unused code, unsafe patterns and
template problems. This PR adds the tooling and configuration only; the existing
findings are fixed in follow-up PRs before the check is enforced in CI.

Tests

  • npm run format:check passes and npm ci --dry-run succeeds.
  • npm run lint runs and reports 132 existing findings. CI does not run it yet.
  • No source files are changed.
## What - Add ESLint 10 with angular-eslint 21, typescript-eslint and the default Angular rule sets (`ng add angular-eslint@21`), including the `lint` npm script and the `lint` target in `angular.json`. - Do not enforce a selector prefix: the components use mixed prefixes (`app-`, `component-`, none), so `prefix` is an empty array in both selector rules. The selector style (kebab-case / camelCase) is still checked. ## Why Prettier only covers formatting. ESLint finds unused code, unsafe patterns and template problems. This PR adds the tooling and configuration only; the existing findings are fixed in follow-up PRs before the check is enforced in CI. ## Tests - `npm run format:check` passes and `npm ci --dry-run` succeeds. - `npm run lint` runs and reports 132 existing findings. CI does not run it yet. - No source files are changed.
chore: add ESLint with angular-eslint to the frontend
All checks were successful
CI / lint (pull_request) Successful in 15s
Details
CI / build (pull_request) Successful in 2m12s
Details
73ae1d4baa 
## What
- Add ESLint 10 with angular-eslint 21, typescript-eslint and the default
  Angular rule sets (`ng add angular-eslint@21`), including the `lint` npm
  script and the `lint` target in `angular.json`.
- Do not enforce a selector prefix: the components use mixed prefixes (`app-`,
  `component-`, none), so `prefix` is an empty array in both selector rules.
  The selector style (kebab-case / camelCase) is still checked.

## Why
Prettier only covers formatting. ESLint finds unused code, unsafe patterns and
template problems. This PR adds the tooling and configuration only; the existing
findings are fixed in follow-up PRs before the check is enforced in CI.

## Tests
- `npm run format:check` passes and `npm ci --dry-run` succeeds.
- `npm run lint` runs and reports 132 existing findings. CI does not run it yet.
- No source files are changed.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
robinp2000/dachshund-auth-provider!23
No description provided.