Add coding-standard and static-analysis tooling config #8

Closed
opened 2026-07-01 00:50:35 +00:00 by manlycucumber · 0 comments
manlycucumber commented 2026-07-01 00:50:35 +00:00 (Migrated from github.com)

Problem

A clean-room engine needs enforced style and type discipline from day one so later contributions stay consistent and analysable.

Acceptance criteria

  • PHP-CS-Fixer (or PHPCS) config committed with an agreed ruleset
  • Static analyser (PHPStan or Psalm) config committed at an agreed level
  • Composer scripts expose lint and analyse entry points
  • Both tools run clean on the initial scaffold

Notes

Node is allowed at build time only; these PHP tools run via composer scripts.

## Problem A clean-room engine needs enforced style and type discipline from day one so later contributions stay consistent and analysable. ## Acceptance criteria - [ ] PHP-CS-Fixer (or PHPCS) config committed with an agreed ruleset - [ ] Static analyser (PHPStan or Psalm) config committed at an agreed level - [ ] Composer scripts expose `lint` and `analyse` entry points - [ ] Both tools run clean on the initial scaffold ## Notes Node is allowed at build time only; these PHP tools run via composer scripts.
Sign in to join this conversation.
No milestone
No project
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
Directorium/Core#8
No description provided.