jens
788ddcd0b5
- Establish feature-based architecture with clear separation between Logic, Data, and Shared layers - Define directory structure conventions for controllers, entities, DTOs, managers, mappers, models, processors, providers, repositories, and services - Implement Symfony 7.4+ compliance with proper Request handling (UI layer only) - Enforce PHP 8+ attributes usage instead of annotations - Set up proper DTO usage in UseCases with immutable properties - Configure repository pattern with interfaces in Logic layer and implementations in Data layer - Implement strict separation of concerns with UI layer handling Request objects exclusively - Define clear naming conventions (PascalCase for feature names) - Add shared components directory for reusable elements across features - Establish HTTP status code constants usage instead of magic numbers - Configure proper file placement for controllers in UI/Frontend, UI/Api, and UI/CLI subdirectories - Enforce modern PHP practices with explicit return types and strict typing This commit lays the foundation for a maintainable, scalable Symfony 7.4+ application following clean architecture principles and modern coding standards.
550 B
550 B
globs, description, alwaysApply
| globs | description | alwaysApply |
|---|---|---|
| src/Data/*/Entity/*.php | This rule requires that when entities are created and the feature name cannot be determined, instead of defaulting to an 'Unknown' directory, developers must actively select or define a proper feature name to maintain clean architectural separation. | true |
When creating entities, if [FeatureName] is unknown, prompt the user to provide a feature name rather than automatically using 'Unknown'. This ensures proper categorization of entities within the feature-based architecture.