Skip to content

docs(boost): place dtos, policies and filament - #51

Merged
danielebarbaro merged 1 commit into
mainfrom
docs/boost-class-placement
Nov 16, 2026
Merged

danielebarbaro merged 1 commit into
mainfrom
docs/boost-class-placement

Conversation

@danielebarbaro

@danielebarbaro danielebarbaro commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Depends on #50, merge that first.

DTOs, policies and Filament classes have no clean-arch generator, and the docs didn't say where they go. So Laravel and Filament put them in app/Policies and app/Filament, outside the layers.

The README gets a new "Classes without a generator" section, and the Boost skill gets the same rules:

  • DTOs go in app/Application/DTOs as readonly classes.
  • A model's policy goes in a Policies folder next to the model. Laravel finds it there on its own.
  • Filament resources, pages and widgets go in app/Infrastructure/Filament. Point the panel provider there before running make:filament-resource, otherwise Filament ignores the namespace and writes to app/Filament.

The Boost guideline only gets a one line pointer to the skill, to stay under its size limit. CHANGELOG updated.

Docs only, no code changes.

@danielebarbaro
danielebarbaro force-pushed the docs/boost-class-placement branch from e9ef55b to 3441652 Compare November 16, 2026 13:09
@danielebarbaro
danielebarbaro force-pushed the feat/install-migrate-app branch from 0117991 to 0ed1d19 Compare November 16, 2026 13:09
Base automatically changed from feat/install-migrate-app to main November 16, 2026 13:18
@danielebarbaro
danielebarbaro merged commit 3441652 into main Nov 16, 2026
8 of 16 checks passed
@danielebarbaro
danielebarbaro deleted the docs/boost-class-placement branch November 16, 2026 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant