BackwardCompatibilityCheck
Deptrac
BackwardCompatibilityCheck | Deptrac | |
---|---|---|
3 | 16 | |
562 | 2,566 | |
0.9% | 1.6% | |
8.3 | 6.2 | |
15 days ago | 1 day 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.
BackwardCompatibilityCheck
-
Some thoughts on the Interface Default Methods RFC
It's also not a big risk because if it does fail it will fail every time you just load the class that implements the interface so probably your while site will error. If you do cursory testing of the new version before you deploy it you can find the problem quickly before it becomes a problem. You can also do static analysis checks on your code to make sure its compatible with the libraries you use including when you upgrade them. And library maintainers can run Roave/BackwardCompatibilityCheck/ to make sure they don't accidentally introduce a new interface method without declaring a new major version.
-
PHP libraries and tools
roave/backward-compatibility-check: Tool to compare two revisions of a class API to check for BC breaks
-
PHP 8.1 is getting Enums, and here is an article about Enums in depth
btw when I talk about breaking BC I don't really mean not compatible with something stored in the DB using a previous version of the code. I mean not compatible with other PHP code written to work with a previous version of the code. It's the sort of issue https://github.com/Roave/BackwardCompatibilityCheck exists to detect, and for which semver says you have to increase the major version number on a library.
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.
What are some alternatives?
Spout - Read and write spreadsheet files (CSV, XLSX and ODS), in a fast and scalable way
PHP Architecture Tester - PHP Architecture Tester - Easy architecture testing for PHP :heavy_check_mark:
psalm-plugin-phpunit - A PHPUnit plugin for Psalm
modular-laravel - Modular Laravel - Boilerplate project starter
psalm-plugin-doctrine - Stubs to let Psalm understand Doctrine better
phpstan-rules - 👓 Provides a composer package with rules for phpstan/phpstan.
local-php-security-checker - PHP security vulnerabilities checker
phpstan-magento - Magento specific extension for PHPStan
SecurityAdvisories - :closed_lock_with_key: Security advisories as a simple composer exclusion list, updated daily
phparch
no-leaks - :potable_water: PHPUnit Plugin for detecting Memory Leaks in code and tests
GrumPHP - A PHP code-quality tool