Can not call Auth class inside Scope class in Laravel 5.2

Question

I added External Scope for User Model. Simply created Scope, with the name DeveloperScope

use Illuminate\Database\Eloquent\Scope;
use Illuminate\Database\Eloquent\Builder;
use Illuminate\Database\Eloquent\Model;
use Auth;

class DeveloperScope implements Scope
{
    public function apply(Builder $builder, Model $model)
    {
        if(Auth::user()->id != 1){
            $builder->where('id', '<>', 1);
        }
    }
}

Then, I called this scope for User model.

User Model

use Illuminate\Auth\Authenticatable;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Auth\Passwords\CanResetPassword;
use Illuminate\Contracts\Auth\Authenticatable as AuthenticatableContract;
use Illuminate\Contracts\Auth\CanResetPassword as CanResetPasswordContract;
use Illuminate\Database\Eloquent\SoftDeletes;
use App\Models\Scopes\DeveloperScope;

class User extends Model implements AuthenticatableContract, CanResetPasswordContract
{
    use SoftDeletes;
    use Authenticatable, CanResetPassword;


    protected $table = 'users';

    protected $fillable = ['first_name', 'last_name', 'email', 'password'];

    protected $hidden = ['password', 'remember_token'];

    protected $dates = ['deleted_at'];

    protected static function boot()
    {
        parent::boot();

        static::addGlobalScope(new DeveloperScope);
    }
}

It works well, when I don't use Auth::class inside DeveloperScope class. The reason is that, I just want to hide the main user for another users for all Eloquent methods. Of course, I can use session instead of Auth and retrieve user id. But it is still interesting for me, why browser gives an error: ERR_EMPTY_RESPONSE while using Auth::class ?

mpyw · Accepted Answer · 2019-12-12 05:41:36Z

1

The method what you are looking for is exactly Auth::hasUser(). The method was added in Laravel 5.6 through my PR. (So you need to upgrade Laravel first)

[5.6] Add ability to determine if the current user is ALREADY authenticated without triggering side effects by mpyw · Pull Request #24518 · laravel/framework

use Illuminate\Database\Eloquent\Scope;
use Illuminate\Database\Eloquent\Builder;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Support\Facades\Auth;

class DeveloperScope implements Scope
{
    public function apply(Builder $builder, Model $model)
    {
        if (!Auth::hasUser() || Auth::user()->id != 1) {
            $builder->where('id', '<>', 1);
        }
    }
}

Just call Auth::hasUser() to prevent Auth::user() from causing side effects.

answered Dec 12, 2019 at 5:41

mpyw

5,7744 gold badges34 silver badges36 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Matthias Weiß · Accepted Answer · 2017-01-24 09:21:09Z

0

Try injecting the Illuminate\Auth\Guard class and then call the user method on it. e.g.:

$this->auth->user();

You should be fine with just type-hinting it since Laravel will automatically new up an instance for you.

For more info check out the API: https://laravel.com/api/5.2/Illuminate/Auth/Guard.html

answered Jan 24, 2017 at 9:21

Matthias Weiß

5081 gold badge7 silver badges17 bronze badges

6 Comments

Rashad Over a year ago

As I understand, you mean calling __construct function and retrieve auth. Why inject Guard? We could just inject Auth. But both of them will not work. I tried. Also, it is possible just return Auth::user() from construct. Now, this will work :) But this will duplicate sql.

Matthias Weiß Over a year ago

The Auth facade points to Illuminate\Auth\Guard so that should work. And Auth::user() will not have duplicate SQL because if the user isn't in the session it will fetch it, otherwise it will just receive it from the session store.

Rashad Over a year ago

public function __construct(Guard $auth){$this->auth = $auth->user();} right?

Matthias Weiß Over a year ago

No, just $this->auth = $auth and then use it like this: $this->auth->user();

Rashad Over a year ago

The problem is not coming from construct. in my User model I can't instantiate interface Guard. However, static::addGlobalScope(new DeveloperScope) is missing $auth. Can't figure out how to call $auth in my scope. static::addGlobalScope(new DeveloperScope (new Guard) ) is not working too.

|

Collectives™ on Stack Overflow

Can not call Auth class inside Scope class in Laravel 5.2

2 Answers 2

Comments

6 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

6 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related