Boot parent provider after.

Opting to boot the parent provider after prevents the router binding to be fired
too early. This was causing issues primarily if the service provider was added
to the config after all the other providers.

This caused issues primarily with tests because of the execution order of the
Kernel. Middlewares were not registered on the router instance.

Reference issue dingo#964.

Author: jasonlewis

src/Provider/LaravelServiceProvider.php

@@ -18,8 +18,6 @@ class LaravelServiceProvider extends DingoServiceProvider
      */
     public function boot()
     {
-        parent::boot();
-
         $this->publishes([realpath(__DIR__.'/../../config/api.php') => config_path('api.php')]);
 
         $kernel = $this->app->make('Illuminate\Contracts\Http\Kernel');
@@ -35,6 +33,8 @@ public function boot()
 
             $this->updateRouterBindings();
         });
+
+        parent::boot();
     }
 
     /**

src/Provider/LumenServiceProvider.php

@@ -16,8 +16,6 @@ class LumenServiceProvider extends DingoServiceProvider
      */
     public function boot()
     {
-        parent::boot();
-
         $this->app->configure('api');
 
         $reflection = new ReflectionClass($this->app);
@@ -47,6 +45,8 @@ public function boot()
             'api.throttle' => 'Dingo\Api\Http\Middleware\RateLimit',
             'api.controllers' => 'Dingo\Api\Http\Middleware\PrepareController',
         ]);
+
+        parent::boot();
     }
 
     /**