addiks/symfony_generics

A collection of generic configurable PHP components

v0.21.1 2023-02-14 15:04 UTC

Requires

• php: >=8.1
• doctrine/orm: ^2.6 || ^2.7 || ^2.8 || ^2.9 || ^2.14
• psr/container: ^1.0 || ^2.0
• symfony/form: ^4.4 || ^5.3 || ^6.2
• symfony/framework-bundle: ^4.4 || ^5.3 || ^6.2
• symfony/http-foundation: ^v4.4 || ^5.3 || ^6.2
• symfony/property-access: ^4.4 || ^5.3 || ^6.2
• symfony/security-bundle: ^4.4 || ^5.3 || ^6.2
• symfony/serializer: ^4.4 || ^5.3 || ^6.2
• twig/twig: ^2.13 || ^2.14 || ^3.0 || ^3.1 || ^3.2 || ^3.3 || ^3.5
• webmozart/assert: ^1.3

Requires (Dev)

• infection/infection: *
• phpstan/phpstan: *
• phpunit/phpunit: ^9.5
• vimeo/psalm: *

MIT

README

Symfony Generic Components

This is a collection of configurable generic components to use for symfony. (Currently it mostly consists of generic controllers.) I believe that as a developer you should focus your work as much as possible to model and mold your domain of choice into software. Other technical necessities (such as controllers) should be reduced as much as possible.

The generic components in this library are built in a way that they can be re-used multiple times in different configurations to replace components in your software that you would otherwise would have to build from scratch. This not only saves you time, it also improves the quality of your software because all the components in this library are fully tested and thus by extension a bigger part of your application becomes tested.

Additionally, if you use generic components instead of writing everything by hand, your application becomes more uniform and machine-readable & -interpretable. For example: If you use generic controllers it is easy to tell which controllers just render a template, you could write a smoke-test that just executes all template-render-controllers and checks if any errors happen. Because you know that these controllers just render a template and do nothing else, you know that you can execute them without side-effect. Without doing much, you would have already tested a big portion of your application. (I actually plan to include such a smoke-test in this library in the future.)

In short, these are the advantages of using this library:

• Less code to write and maintain
• More time for the things that make your software unique
• A bigger part of your application will be battle-tested
• More standardized parts that other developers will know how to work with

These components currently exist in the library: