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

chore: format the frontend with Prettier #21

Merged
robinp2000 merged 1 commit from robinp2000/chore/format-frontend into main 2026-10-16 01:13:13 +02:00 AGit
Conversation 0 Commits 1 Files changed 72 +1579 -776
robinp2000 commented 2026-10-15 18:52:19 +02:00
Owner
Copy link

What

Run prettier --write . in frontend/ with the existing .prettierrc and
.editorconfig. 72 files change (70 under src/, plus tsconfig.app.json and
tsconfig.spec.json). Formatting only: no config, dependency or logic changes.

Why

Prettier is installed and configured but was never applied, so 72 files deviate
from the project style. Reformatting in its own PR keeps the follow-up PR
(scripts and CI check) free of noise and the squash commit a pure formatting change.

Tests

  • ng build succeeds.
  • prettier --check . reports no remaining differences.
  • There are no frontend unit tests (ng test finds no spec files).

Notes

  • ng build reports two component-style budget warnings
    (email-provider.component.scss, authenticated.page.scss). Both already
    exist on main, and the reported sizes are identical before and after this change.
  • The format scripts and the CI check follow in a separate PR.
## What Run `prettier --write .` in `frontend/` with the existing `.prettierrc` and `.editorconfig`. 72 files change (70 under `src/`, plus `tsconfig.app.json` and `tsconfig.spec.json`). Formatting only: no config, dependency or logic changes. ## Why Prettier is installed and configured but was never applied, so 72 files deviate from the project style. Reformatting in its own PR keeps the follow-up PR (scripts and CI check) free of noise and the squash commit a pure formatting change. ## Tests - `ng build` succeeds. - `prettier --check .` reports no remaining differences. - There are no frontend unit tests (`ng test` finds no spec files). ## Notes - `ng build` reports two component-style budget warnings (`email-provider.component.scss`, `authenticated.page.scss`). Both already exist on `main`, and the reported sizes are identical before and after this change. - The `format` scripts and the CI check follow in a separate PR.
chore: format the frontend with Prettier
All checks were successful
CI / build (pull_request) Successful in 2m7s
Details
09545b522a 
## What
Run `prettier --write .` in `frontend/` with the existing `.prettierrc` and
`.editorconfig`. 72 files change (70 under `src/`, plus `tsconfig.app.json` and
`tsconfig.spec.json`). Formatting only: no config, dependency or logic changes.

## Why
Prettier is installed and configured but was never applied, so 72 files deviate
from the project style. Reformatting in its own PR keeps the follow-up PR
(scripts and CI check) free of noise and the squash commit a pure formatting change.

## Tests
- `ng build` succeeds.
- `prettier --check .` reports no remaining differences.
- There are no frontend unit tests (`ng test` finds no spec files).

## Notes
- `ng build` reports two component-style budget warnings
  (`email-provider.component.scss`, `authenticated.page.scss`). Both already
  exist on `main`, and the reported sizes are identical before and after this change.
- The `format` scripts and the CI check follow in a separate PR.
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!21
No description provided.