Laravel 5.2 binding session object to router

I don't think you're supposed to do route model binding in RouteServiceProvider@map. According to the documentation, you're supposed to do it in RouteServiceProvider@boot:

    /**
     * Define your route model bindings, pattern filters, etc.
     *
     * @param  \Illuminate\Routing\Router  $router
     * @return void
     */
    public function boot(Router $router)
    {
        parent::boot($router);
        
        $router->bind('carts', function ($value) {
            return Cart::get($value);
        });
    }

@jhoff , Yep i had tried that aswell. Session is still not loaded. In fact its not loaded until i run the Cart::get($value) from my controller. Do you have any other ideas,maybe?

Are your routes using the new web middleware?

Route::group(['middleware' => 'web'], function() {
    Route::resource('carts', 'CartsController');
});

@jhoff , YES :/

@jhoff , can you check it for yourself if the Session is loaded in router or not?

The default web middleware should be starting the Session:

app\Http\Kernel.php

    protected $middlewareGroups = [
        'web' => [
            ...
            \Illuminate\Session\Middleware\StartSession::class,

Maybe it's an issue with using the facade? Does it work to use app()->session() instead?

AFAIK, your middlewares wont be called unless the service providers are registered and booted. So no session iinfo will be available for you to use.

Well, first, there are a few things that I would change or a few things that I just don't understand.

1. You named your function get. It's kind of confusing because it behaves vastly different from Laravel's own get method.

2. I'm assuming $cartId is an integer. Laravel model's constructor function accepts an array, not an integer.

Finally, regarding your problem, you cannot use sessions inside the RouteServiceProvider because Laravel sessions haven't even been initialized yet. There's a huge discussion on that here:

https://github.com/laravel/framework/issues/6118

Basically, people are saying that it doesn't make sense to run route model binding before middlewares (which is what initiates the sessions). Some are arguing that it does make sense.

In L5.2, this lifecycle kind of caused other issues with the new implicit model binding.

Anyway, a workaround is to move the web middleware into the global middleware stack. This means getting rid of your web middleware. So open up app\Http\Kernel.php and change these two arrays:

    protected $middleware = [
        \Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::class,
        \App\Http\Middleware\EncryptCookies::class,
        \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
        \Illuminate\Session\Middleware\StartSession::class,
        \Illuminate\View\Middleware\ShareErrorsFromSession::class,
        \App\Http\Middleware\VerifyCsrfToken::class,
    ];
    protected $middlewareGroups = [
        'api' => [
            'throttle:60,1',
        ],
    ];

Also, make sure to remove the web group in your routes file.

thanks for the info @thomaskim , I tried adding StartSession middleware to global middleware stack. That didn't help either. I'm gonna try putting all the middlewares from web to global. Hope that will help. and for the record, Cart is not a Modal class, its my own class in different namespace .

Oh okay. Sorry, didn't know that about your Cart class.

Regarding the middlewares, yes, my example moved the entire web group to the global middleware stack. :)

can somebody help me with my route model binding issue? https://laracasts.com/discuss/channels/laravel/implicit-model-binding-custom-resolve-for-some-methods#