Code Quality Configuration

This page is a reference for the three configuration files that govern code style enforcement, editor behavior, and repository distribution in this package: pint.json, .editorconfig, and .gitattributes. These files apply uniformly to all source files in the repository.

For information on how linting is exercised in automated pipelines, see CI/CD Pipeline. For the testing configuration that complements the quality tooling, see Testing Configuration. For contribution expectations that depend on these rules, see Contributing Guidelines.

---

Laravel Pint (pint.json)

pint.json configures Laravel Pint, the opinionated PHP code style fixer built on top of PHP-CS-Fixer.

Source: pint.json1-8

Field	Value	Effect
preset	"laravel"	Applies all rules from the official Laravel coding standard
no_unused_imports	false	Disables auto-removal of unused use statements
strict_comparison	true	Enforces === and !== instead of == and !=
declare_strict_types	true	Requires declare(strict_types=1); at the top of every PHP file

The no_unused_imports rule is explicitly turned off. This is common in packages that pre-import types for IDE support or that use imports conditionally through traits.

The two enabled rules (strict_comparison and declare_strict_types) raise the type safety floor beyond the base Laravel preset. Every .php file in src/ is expected to carry a strict types declaration.

Running the linter locally:

Composer script	Behavior
composer lint	Runs Pint and auto-fixes violations
composer test:lint	Runs Pint in --test mode (read-only, exits non-zero on violations)

These scripts are defined in composer.json and are also exercised by the lint.yml GitHub Actions workflow on pushes to main.

Diagram: Pint Rule Inheritance

Sources: pint.json1-8

---

EditorConfig (.editorconfig)

.editorconfig provides editor-agnostic formatting rules that apply automatically in any compatible editor (PhpStorm, VS Code, Neovim, etc.). It does not require a separate tool installation.

Source: .editorconfig1-13

Global rules ([*])

Property	Value	Meaning
charset	utf-8	All files use UTF-8 encoding
end_of_line	lf	Unix-style line endings (LF, not CRLF)
indent_size	4	Four spaces per indent level
indent_style	space	Spaces, not tabs
insert_final_newline	true	Every file ends with a newline character
trim_trailing_whitespace	true	No trailing spaces on any line

File-type overrides

Pattern	Override	Reason
[*.md]	trim_trailing_whitespace = false	Markdown uses two trailing spaces for line breaks
[*.{yml,yaml}]	indent_size = 2	YAML convention uses 2-space indentation

The 2-space YAML override applies to files such as testbench.yaml and the GitHub Actions workflow files under .github/workflows/.

Diagram: EditorConfig Rule Applicability

Sources: .editorconfig1-13

---

Git Attributes (.gitattributes)

.gitattributes serves two purposes: it assigns diff drivers to specific file types for more readable git diff output, and it controls which files are excluded from composer install distribution archives via export-ignore.

Source: .gitattributes1-17

Line ending normalization

* text=auto

Instructs Git to auto-detect and normalize line endings on checkout. This pairs with the .editorconfig LF setting.

Diff strategy assignments

Pattern	Diff driver	Effect
*.blade.php	html	HTML-aware diff output for Blade templates
*.md	markdown	Markdown-aware diff output
*.php	php	PHP-aware diff output

These assignments make git diff and pull request diffs more semantically accurate for each file type.

Export-ignore list

Files and directories marked export-ignore are excluded when composer creates a distribution archive (e.g., from a git archive or a Packagist release). Only the production runtime files are included in the installed package.

Entry	Type	Rationale
/.github	Directory	CI workflows, MCP config — dev-only
/tests	Directory	Test suite — not needed by consumers
.editorconfig	File	Editor settings — not needed by consumers
.gitattributes	File	Git metadata — not needed by consumers
.gitignore	File	Git metadata — not needed by consumers
phpunit.xml	File	Test configuration — not needed by consumers
pint.json	File	Linter configuration — not needed by consumers
boost.json	File	Development boost config — not needed by consumers
testbench.yaml	File	Testbench configuration — not needed by consumers
/workbench	Directory	Local dev workbench app — not needed by consumers

Diagram: Distribution Archive Contents

Sources: .gitattributes1-17

---

Summary

File	Tool/Spec	Primary function
pint.json	Laravel Pint (PHP-CS-Fixer)	PHP code style rules; enforces strict types and strict comparison
.editorconfig	EditorConfig spec	Cross-editor whitespace, encoding, and newline consistency
.gitattributes	Git	Diff strategies per file type; excludes dev files from distribution

All three files operate at the repository level and apply to contributors and tooling alike. They are themselves excluded from distribution releases via the export-ignore directives in .gitattributes.