olindn / laravel-fitbit

Laravel wrapper for namelivia/fitbit-http-php

laravel-fitbit

Installation

Require this package, with Composer, in the root directory of your project.

$ composer require namelivia/laravel-fitbit

Add the service provider to config/app.php in the providers array. If you're using Laravel 5.5 or greater, there's no need to do this.

Namelivia\Fitbit\Laravel\FitbitServiceProvider::class

If you want you can use the facade. Add the reference in config/app.php to your aliases array.

'Fitbit' => Namelivia\Fitbit\Laravel\Facades\Fitbit::class

Configuration

Laravel Fitbit requires connection configuration. To get started, you'll need to publish all vendor assets:

$ php artisan vendor:publish --provider="Namelivia\Fitbit\Laravel\FitbitServiceProvider"

This will create a config/fitbit.php file in your app that you can modify to set your configuration. Also, make sure you check for changes to the original config file in this package between releases.

Default Connection Name

This option default is where you may specify which of the connections below you wish to use as your default connection for all work. Of course, you may use many connections at once using the manager class. The default value for this setting is main.

Fitbit Connections

This option connections is where each of the connections are setup for your application. Example configuration has been included, but you may add as many connections as you would like.

Usage

FitbitManager

This is the class of most interest. It is bound to the ioc container as fitbit and can be accessed using the Facades\Fitbit facade. This class implements the ManagerInterface by extending AbstractManager. The interface and abstract class are both part of Graham Campbell's Laravel Manager package, so you may want to go and checkout the docs for how to use the manager class over at that repository. Note that the connection class returned will always be an instance of Api.

Facades\Fitbit

This facade will dynamically pass static method calls to the fitbit object in the ioc container which by default is the FitbitManager class.

FitbitServiceProvider

This class contains no public methods of interest. This class should be added to the providers array in config/app.php. This class will setup ioc bindings.

Examples

Here you can see an example of just how simple this package is to use. Out of the box, the default adapter is main. After you enter your authentication details in the config file, it will just work:

// You can alias this in config/app.php.
use Namelivia\Fitbit\Laravel\Facades\Fitbit;

Fitbit::activities()->activity()->getLifetimeStats();
// We're done here - how easy was that, it just works!

The Fitbit manager will behave like it is a Fitbit. If you want to call specific connections, you can do that with the connection method:

use Namelivia\Fitbit\Laravel\Facades\Fitbit;

// Writing this…
Fitbit::connection('main')->activities()->activity()->getLifetimeStats();

// …is identical to writing this
Fitbit::activities()->activity()->getLifetimeStats();

// and is also identical to writing this.
Fitbit::connection()->activities()->activity()->getLifetimeStats();

// This is because the main connection is configured to be the default.
Fitbit::getDefaultConnection(); // This will return main.

// We can change the default connection.
Fitbit::setDefaultConnection('alternative'); // The default is now alternative.

If you prefer to use dependency injection over facades like me, then you can inject the manager:

use Namelivia\Fitbit\Laravel\FitbitManager;

class Foo
{
    protected $fitbit;

    public function __construct(FitbitManager $fitbit)
    {
        $this->fitbit = $fitbit;
    }

    public function bar()
    {
        $this->fitbit->activities()->activity()->getLifetimeStats();
    }
}

App::make('Foo')->bar();

Documentation

This is package is a Laravel wrapper of fitbit-http-php.

License

MIT

Local development

This project comes with a docker-compose.yml file so if you use Docker and docker-compose you can develop without installing anything on your local environment. Just run docker-compose up --build for the first time to setup the container and launch the tests. PHPUnit is configured as the entrypoint so just run docker-compose up everytime you want the tests to execute on the Dockerized PHP development container.