BackwardCompatibilityCheck
composer-normalize
BackwardCompatibilityCheck | composer-normalize | |
---|---|---|
3 | 6 | |
562 | 1,011 | |
0.9% | 0.8% | |
8.3 | 9.4 | |
13 days ago | 8 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.
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.
composer-normalize
-
Elevate Your PHP Development Game with Composer Tips
Composer-Normalize: Your Organization Sidekick! Let's talk about keeping things neat and tidy! Enter Composer-Normalize. This nifty tool ensures your composer.json file stays impeccably organized and sorted. No more chaotic dependency lists - it's all about that clean, structured vibe! ππ More info here: https://github.com/ergebnis/composer-normalize
-
The "pds/composer-script-names" standard is now stable
I guess composer normalize is doing those checks since it is validating the composer.json against it's official schema. More at https://github.com/ergebnis/composer-normalize
-
Users of VS Code, what Composer-related features would you like to see?
Use composer-normalize as a formatter
-
PHP libraries and tools
composer-normalize: Provides a composer plugin for normalizing composer.json.
-
Create or Update PR Action
The README itself shows that itβs being used to keep track of Chinese Starbucks stores, download JSON schema updates periodically and even by the Node project itself to keep the license file up to date.
What are some alternatives?
Spout - Read and write spreadsheet files (CSV, XLSX and ODS), in a fast and scalable way
Composer Merge Plugin - Merge one or more additional composer.json files at Composer runtime
psalm-plugin-phpunit - A PHPUnit plugin for Psalm
NameSpacer - PHP Class converter to namepaces.
psalm-plugin-doctrine - Stubs to let Psalm understand Doctrine better
Satis - Simple static Composer repository generator - For a full private Composer repo use Private Packagist
local-php-security-checker - PHP security vulnerabilities checker
Patch Installer - Patch other composer packages on install or update
SecurityAdvisories - :closed_lock_with_key: Security advisories as a simple composer exclusion list, updated daily
Prestissimo - composer parallel install plugin
no-leaks - :potable_water: PHPUnit Plugin for detecting Memory Leaks in code and tests