jeroendesloovere/volleyadmin2-php-api

This VolleyAdmin2 class can get the volleybal matches/calendar in Belgium for the KWVBV.

VolleyAdmin2 PHP API

, _(*1)

This PHP class can get the volleybal matches/calendar from the VolleyAdmin2 API., _(*2)

Usage

Installation

composer require jeroendesloovere/volleyadmin2-php-api

This will install the latest version of this library using Composer., _(*3)

Example

``` php use JeroenDesloovere\VolleyAdmin2\VolleyAdmin2;, <sub>(*4)</sub>

// Fill in these custom variables $clubNumber = 'W-1132'; $provinceId = 9; $seriesId = '2 PDA'; // Tweede provinciale dames A, <sub>(*5)</sub>

$api = new VolleyAdmin2();, <sub>(*6)</sub>

$matches = $api->getMatches( $seriesId, $provinceId, $clubNumber );, <sub>(*7)</sub>

$series = $api->getSeries($provinceId);, <sub>(*8)</sub>

$standings = $api->getStandings( $seriesId, $provinceId );, <sub>(*9)</sub>

> [View all examples](/examples/) or check [the VolleyAdmin2 class](/src/).

### Tests

You can execute the tests using:
``` bash
vendor/bin/phpunit tests

Coding Syntax

We use squizlabs/php_codesniffer to maintain the code standards. Type the following to execute them:, <sub>(*10)</sub>

# To view the code errors
vendor/bin/phpcs --standard=psr2 --extensions=php --warning-severity=0 --report=full "src"

# OR to fix the code errors
vendor/bin/phpcbf --standard=psr2 --extensions=php --warning-severity=0 --report=full "src"

Read documentation about the code standards, <sub>(*11)</sub>

Documentation

The class is well documented inline. If you use a decent IDE you'll see that each method is documented with PHPDoc., <sub>(*12)</sub>

Contributing

Contributions are welcome and will be fully credited., <sub>(*13)</sub>

Pull Requests

To add or update code, <sub>(*14)</sub>

• Coding Syntax - Please keep the code syntax consistent with the rest of the package.
• Add unit tests! - Your patch won't be accepted if it doesn't have tests.
• Document any change in behavior - Make sure the README and any other relevant documentation are kept up-to-date.
• Consider our release cycle - We try to follow semver. Randomly breaking public APIs is not an option.
• Create topic branches - Don't ask us to pull from your master branch.
• One pull request per feature - If you want to do more than one thing, send multiple pull requests.
• Send coherent history - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before submitting.

Issues

For bug reporting or code discussions., <sub>(*15)</sub>

More info on how to work with GitHub on help.github.com., <sub>(*16)</sub>

Credits

• Jeroen Desloovere
• All Contributors

License

The module is licensed under MIT. In short, this license allows you to do everything as long as the copyright statement stays present., <sub>(*17)</sub>