Search bug fixes

- Replaced 'spotify-web-api-php' wrapper with newer version.

vendor/jwilsson/spotify-web-api-php/.travis.yml

@@ -1,25 +1,28 @@
 language: php
 
 php:
- - 5.3
- - 5.4
  - 5.5
  - 5.6
+ - 7.0
+ - 7.1
+ - nightly
  - hhvm
 
+sudo: false
+
 matrix:
  fast_finish: true
-
-before_install:
- - openssl aes-256-cbc -K $encrypted_02ebdc0031ce_key -iv $encrypted_02ebdc0031ce_iv -in .env.enc -out .env -d
+ allow_failures:
+ php: nightly
 
 before_script:
  - travis_retry composer self-update
  - travis_retry composer install --prefer-dist --no-interaction
 
 script:
  - mkdir -p build/logs
- - vendor/bin/phpunit --verbose --coverage-clover build/logs/clover.xml
+ - vendor/bin/phpcs src -v --standard=PSR2
+ - vendor/bin/phpunit
 
 after_script:
  - php vendor/bin/coveralls -v

vendor/jwilsson/spotify-web-api-php/CONTRIBUTING.md

@@ -4,14 +4,37 @@
 Please submit all your bug reports, feature requests and pull requests here but note that this isn't the place for support requests. Please use [Stack Overflow](http:https://stackoverflow.com/) for this.
 
 ## Bug reports
-1. Search the issues, have it already been reported?
+1. Search the issues, has it already been reported?
 2. Download the latest source, did this solve the problem?
 4. If the answer to all of the above questions are "No" then open a bug report and include the following:
  * A short, descriptive title.
  * A summary of the problem.
  * The steps to reproduce the problem.
  * Possible solutions or other relevant information/suggestions.
 
+## New features
+If you have an idea for a new feature, please file an issue first to see if it fits the scope of this project. That way no one's time needs to be wasted.
+
 ## Coding Guidelines
-We follow the coding standards outlined in [PSR-1](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md) and [PSR-2](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md). Please follow these guidelines when commiting new code.
-Fixes for existing code which doesn't follow these standards are highly appreciated!
+We follow the coding standards outlined in [PSR-1](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md) and [PSR-2](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md). Please follow these guidelines when committing new code.
+
+In addition to the PSR guidelines we try to adhere to the following points:
+* We order all methods by visibility and then alphabetically, `private`/`protected` methods first and then `public`. For example:
+
+```
+protected function b() {}
+
+public function a() {}
+```
+
+instead of
+
+```
+public function a() {}
+
+protected function b() {}
+```
+
+* We strive to keep the inline documentation language consistent, take a look at existing docs for examples.
+
+Before committing any code, be sure to run `composer test` to ensure that the code style is consistent and all the tests pass.