Our great sponsors
Deptrac | GrumPHP | |
---|---|---|
16 | 25 | |
2,551 | 4,088 | |
2.0% | 0.5% | |
6.8 | 8.0 | |
11 days ago | 23 days ago | |
PHP | PHP | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Deptrac
- Microservices aren't the problem. Incompetent people are
-
Enforce architecture rules with Deptrac
Deptrac
-
PHP libraries and tools
Deptrac: Keep your architecture clean.
-
Enforcing module boundaries in a large php app
So far I've found some tools which I could piece together to accomplish enforcing module boundaries, probably run as part of an automated github action. - https://github.com/qossmic/deptrac Uses YAML to define any boundary, you can also use @internal to hide implementation classes. Seems like a good way to achieve what I want.
- Deptrac - architectural code analysis
- Deptrac - architectural static code analysis
- Deptrac, the is a static code analysis tool to enforce architectural decisions had version 1.0.0 released!
-
Best way to check custom coding conventions
How about https://qossmic.github.io/deptrac/ ?
-
The use of `class` for things that should be simple free functions (2020)
>I wonder: Is automatic DI even helpful? You save some lines of boilerplate but sacrifice control over the initialization-order and get a flat, messy, implicit dependency graph
Initialization order doesn't matter if your services are stateless. At least in our codebase, all of them are stateless, as it greatly simplifies reasoning about concurrent code (both in-process and between servers). Yes, it's easy to end up with a very a convoluted dependency graph under the hood, but I don't think it's a problem you really should care about. I mean, your code most likely already compiles to a very convoluted mess of machine code under the hood (with all the optimizations, ABI quirks etc.) and I doubt it matters to you much, as long as it does its job well and doesn't hinder your productivity.
If you are talking about messy dependency graphs from the architectural standpoint (someone can easily add a dependency in the constructor without thinking about the consequences), we use deptrac for our PHP monolith which can validate your architecture is clean at build time [0]
However, for our microservices written in Go, we decided to use manual DI to stimulate developers to prefer simpler design, otherwise our microservices could quickly turn to monoliths again.
[0] https://github.com/qossmic/deptrac
-
The 4 basic libraries every Symfony Project needs to improve code quality
Deptrac is a static code analysis tool for PHP that helps you communicate, visualize and enforce architectural decisions in your projects.
GrumPHP
-
PHP libraries and tools
GrumPHP: A PHP code-quality tool.
-
Recommended Code Review Plugin for Github?
Depends on what you mean by plugin, but a GrumPHP is a great tool. It registers a pre-commit git hook that runs whatever quality tools you've configured every time someone commits. If one of the checks fail, the commit is aborted. It's very easy to install and configure.
- Looking to build a code quality tool for Laravel - opinions wanted
-
PHPUnit, do i need to learn it?
sounds like you heard of Grumphp
- Ideas for minimum PHP pipeline for a small team
-
Ensure a beaut code with Laravel Pint
Of course, in this simple way, you will need run the command before commits to ensure a correct code style. We can improve this we can to use some pre-commit hook, like a grumphp https://github.com/phpro/grumphp.
-
A quality inspection hook installer
How does this compare to existing tools like GrumPHP or Captain Hook? Why should I use it instead?
Are you aware of GrumPHP?
-
Is there a way to run commands before PHPStorm commits?
I use grumphp to run phplint, phpstan, Easy coding standard (includes php-cs fixer) and phpunit. All four will automatically run before every commit, stopping any 'below standard' code from being committed. Example config file
-
What are some helpful tools every Laravel CI pipeline should have?
like valplet said: https://github.com/phpro/grumphp But also: https://styleci.io/ integrates nicely with git For client side code formatting check: https://prettier.io/
What are some alternatives?
PHP Architecture Tester - PHP Architecture Tester - Easy to use architectural testing tool for PHP :heavy_check_mark:
PHPStan - PHP Static Analysis Tool - discover bugs in your code without running it!
modular-laravel - Modular Laravel - Boilerplate project starter
PHP CS Fixer - A tool to automatically fix PHP Coding Standards issues
phpstan-rules - 👓 Provides a composer package with rules for phpstan/phpstan.
PHP Code Sniffer - PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards.
phpstan-magento - Magento specific extension for PHPStan
PHPCPD - Copy/Paste Detector (CPD) for PHP code.
phparch
drupal-project - :rocket: Composer template for Drupal projects. Quick installation via "composer create-project drupal-composer/drupal-project"
psalm-plugin-phpunit - A PHPUnit plugin for Psalm
PHP Mess Detector - PHPMD is a spin-off project of PHP Depend and aims to be a PHP equivalent of the well known Java tool PMD. PHPMD can be seen as an user friendly frontend application for the raw metrics stream measured by PHP Depend.