| CARVIEW |
The League of Extraordinary Packages is a group of developers who have banded together to build solid, well tested PHP packages using modern coding standards.
★★★- We comply to the standards of the PHP-FIG.
- We adhere to the best-practices put forward by PHP The "Right" Way.
- We distribute code via Packagist and Composer.
Our Packages
-
Name
Description
Project Lead
-
Terminal output made easy
-
Extract colors from an image
-
Markdown parser for PHP based on the CommonMark spec
-
Simple yet expressive schema-based configuration library
-
Fast and intuitive dependency injection container
-
CSV data manipulation made easy
-
Event package for your app and domain
-
Enables the rapid creation of objects for testing
-
Abstraction for local and remote filesystems
-
Output complex, flexible, RESTful data structures
-
Perform geo-related tasks
-
HTTP based image manipulations
-
Converts HTML to Markdown for your sanity and convenience
-
A PHP library providing ISO 3166-1 data.
-
Simple and swift MongoDB abstraction
-
Integrate with OAuth 1.0 providers
-
Build an OAuth 2.0 server
-
Integrate with OAuth 2.0 providers
-
Multi-gateway payment processing library
-
Time range API for PHP
-
Compose sequential tasks with Pipeline.
-
Native PHP template system
-
Router and Dispatcher built on FastRoute
-
Library for working with StatsD
-
A simple, flexible command bus
-
URI manipulation made easy
Our Definition Of Quality
-
Use a vendor namespace (
Leaguein our case) for PSR-4 autoloading. Shove code in asrcfolder. -
Adhere to PSR-2 as the coding style guide.
-
Distribute code using Packagist.
-
Write unit tests. Aim for at least 80% coverage in version 1.
-
DocBlock all the things that require additional context.
-
Use Semantic Versioning to manage version numbers.
-
Keep a Changelog.
-
Use Travis-CI to automatically check coding standards and run tests.
-
Have an extensive README.
Why?
We’re doing this instead of releasing code under our personal accounts for a few reasons, but the main reason is this:
A problem shared is a problem halved.
Working together we take care of business quicker, can get more feedback and respond to issues and pull requests faster.
There are no plans to reinvent any wheels, unless those wheels are old, broken, unsafe or horrible to use. If the code cannot be installed with Composer, has an API written with BizZaroCapS, doesn’t have a single unit-test, is actually broken or the lead developer has abandoned the project, then that is a problem which can most likely be solved with a fresh start, and we’ll be on the case to make it as awesome as possible.