Add CheckScopes and CheckForAnyScope Middleware

[filippofortino]

This PR add the CheckScopes middleware and CheckForAnyScopes middleware from Passport.
The code is basically copy-pasted from Passport.

This idea was discussed earlier today by @masterix21 and @themsaid on Twitter.

https://twitter.com/masterix21/status/1448212135578935296

[driesvints]

@filippofortino I just released this. Can you also PR this to the docs of Sanctum? Thanks!

[filippofortino]

@filippofortino I just released this. Can you also PR this to the docs of Sanctum? Thanks!

Sure, don't know if i'm gonna be able to do that today, but will do it by tomorrow.

I was thinking however, since Sanctum refers to scopes as abilities, would it be better to rename this two middlewares to CheckAbility and CheckForAnyAbilities?

Of course you can already register them like so in app/Http/Kernel.php and use it your app, but idk, i just thought it was wort mentioning.

'abilities' => \Laravel\Sanctum\Http\Middleware\CheckScopes::class,
'ability' => \Laravel\Sanctum\Http\Middleware\CheckForAnyScope::class

Let me know what you think and i can send a PR in case you agree.

[driesvints]

You can always try to see if Taylor would accept it 👍

[masterix21]

I was thinking however, since Sanctum refers to scopes as abilities, would it be better to rename this two middlewares to CheckAbility and CheckForAnyAbilities?

I think it would break a lot of applications.

[driesvints]

@masterix21 this PR is just a week old

[masterix21]

@driesvints I'm talking about the idea to replace CheckScopes and CheckForAnyScope with *Ability.

[filippofortino]

@driesvints I'm talking about the idea to replace CheckScopes and CheckForAnyScope with *Ability.

This will only replace the newly added middlewares in Sanctum, if you're using the ones in Passport they won't be affected.

However, I'll send a PR later today and we'll see.

[driesvints]

@filippofortino a BC solution for now would be to move the functionality to the new traits and then re-use those traits in the old ones. Then add a @deprecated annotation to the old traits to point people to the new ones. We can then remove them in the next major version.

[filippofortino]

@driesvints alright I'll do that!