38 lines
948 B
Markdown
38 lines
948 B
Markdown
# Quality Guidelines
|
|
|
|
> Code quality standards for frontend development.
|
|
|
|
---
|
|
|
|
## Overview
|
|
|
|
The workbench frontend uses Prettier as the source formatting authority. Code is formatted before review; formatting is not left to individual editor settings.
|
|
|
|
---
|
|
|
|
## Forbidden Patterns
|
|
|
|
- Do not commit dense, manually minified, or single-line JSX/TypeScript.
|
|
- Do not hand-format around Prettier output.
|
|
|
|
---
|
|
|
|
## Required Patterns
|
|
|
|
- Run `npm run format` after editing frontend files.
|
|
- Run `npm run format:check` in the validation gate.
|
|
- Keep React components, hooks, types, and API clients in separately formatted modules once a component becomes non-trivial.
|
|
|
|
---
|
|
|
|
## Testing Requirements
|
|
|
|
- Run `npm run format:check`, `npm run test:client`, and `npm run build` for frontend changes.
|
|
|
|
---
|
|
|
|
## Code Review Checklist
|
|
|
|
- Formatting check passes.
|
|
- UI behavior changes do not rebuild the OpenLayers map unless the map lifecycle explicitly requires it.
|