psalm-plugin-symfony
BackwardCompatibilityCheck
psalm-plugin-symfony | BackwardCompatibilityCheck | |
---|---|---|
3 | 3 | |
221 | 559 | |
0.0% | 0.4% | |
4.6 | 8.3 | |
about 1 month ago | 8 days ago | |
Gherkin | 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.
psalm-plugin-symfony
-
Which framework for a beginnner?
To feel more like home, you will also need static analysis and Symfony plugin. For IDE: use PHPStorm and EA extended plugin. PHP doesn't have generics but those can be emulated via annotations; not a fun way but you get used after a week.
- Why is symfony better for long life big enterprise apps than laravel?
-
PHP libraries and tools
psalm/plugin-symfony: Psalm Plugin for Symfony.
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.
What are some alternatives?
PHPStan - PHP Static Analysis Tool - discover bugs in your code without running it!
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
psalm-plugin-doctrine - Stubs to let Psalm understand Doctrine better
Psalm - A static analysis tool for finding errors in PHP applications
local-php-security-checker - PHP security vulnerabilities checker
SecurityAdvisories - :closed_lock_with_key: Security advisories as a simple composer exclusion list, updated daily
ComposerRequireChecker - A CLI tool to check whether a specific composer package uses imported symbols that aren't part of its direct composer dependencies
no-leaks - :potable_water: PHPUnit Plugin for detecting Memory Leaks in code and tests