You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently implemented a simple pattern that allows us to split our architectural rules across multiple files, making our phparkitect.php setup easier to scale and maintain as our codebase grows.
Each file inside the /architecture folder defines a single function (e.g. clockArchitectureRules, quotingArchitectureRules, etc.) that returns an iterable of rules.
I'm sharing this in case it could inspire a similar built-in feature, or if we'd be interested in documenting this pattern as a recommended practice.
Happy to hear your thoughts!
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
I recently implemented a simple pattern that allows us to split our architectural rules across multiple files, making our
phparkitect.php
setup easier to scale and maintain as our codebase grows.Here’s a simplified version of what we’re doing:
Each file inside the /architecture folder defines a single function (e.g.
clockArchitectureRules
,quotingArchitectureRules
, etc.) that returns an iterable of rules.I'm sharing this in case it could inspire a similar built-in feature, or if we'd be interested in documenting this pattern as a recommended practice.
Happy to hear your thoughts!
The text was updated successfully, but these errors were encountered: