While we added support for both namespaces via vonage/nexmo-bridge, the unit tests were pretty heavily tied to specific class names. This fixes the tests to work better for internal class checking, and as a side consequence makes it possible to create Vonage\Client as well as Nexmo\Client through the service provider.
This is not a customer-facing change, just cleans up the tests. The config options will be altered when we push this as vonage/laravel, and is a psuedo-prerequisite for #51 (I'd like the tests work before we cut another release).
While we added support for both namespaces via
vonage/nexmo-bridge
, the unit tests were pretty heavily tied to specific class names. This fixes the tests to work better for internal class checking, and as a side consequence makes it possible to createVonage\Client
as well asNexmo\Client
through the service provider.This is not a customer-facing change, just cleans up the tests. The config options will be altered when we push this as
vonage/laravel
, and is a psuedo-prerequisite for #51 (I'd like the tests work before we cut another release).