safe8
All PHP functions, rewritten to throw exceptions instead of returning false, now for php8 (by thecodingmachine)
BackwardCompatibilityCheck
:ab: Tool to compare two revisions of a class API to check for BC breaks (by Roave)
safe8 | BackwardCompatibilityCheck | |
---|---|---|
1 | 3 | |
109 | 562 | |
- | 0.9% | |
0.0 | 8.3 | |
over 1 year ago | 12 days ago | |
PHP | PHP | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
safe8
Posts with mentions or reviews of safe8.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-22.
-
PHP libraries and tools
thecodingmachine/safe: All PHP functions, rewritten to throw exceptions instead of returning false, now for php8
BackwardCompatibilityCheck
Posts with mentions or reviews of BackwardCompatibilityCheck.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-28.
-
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.
What are some alternatives?
When comparing safe8 and BackwardCompatibilityCheck you can also consider the following projects:
local-php-security-checker - PHP security vulnerabilities checker
Spout - Read and write spreadsheet files (CSV, XLSX and ODS), in a fast and scalable way
ParaTest - :computer: Parallel testing for PHPUnit
psalm-plugin-phpunit - A PHPUnit plugin for Psalm
GrumPHP - A PHP code-quality tool
psalm-plugin-doctrine - Stubs to let Psalm understand Doctrine better
PHPStan - PHP Static Analysis Tool - discover bugs in your code without running it!