From bdd251a05b4f72737c07b687f5835b2a7e6ce697 Mon Sep 17 00:00:00 2001 From: Chris Withers Date: Sat, 13 Jul 2019 00:17:34 +0100 Subject: [PATCH] :memo: Tweak wording on OAuth2 scopes (#371) --- docs/tutorial/security/oauth2-scopes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tutorial/security/oauth2-scopes.md b/docs/tutorial/security/oauth2-scopes.md index 558212efa..456d53737 100644 --- a/docs/tutorial/security/oauth2-scopes.md +++ b/docs/tutorial/security/oauth2-scopes.md @@ -176,9 +176,9 @@ For this, we use `security_scopes.scopes`, that contains a `list` with all these Let's review again this dependency tree and the scopes. -As the other dependency `get_current_active_user` has as a sub-dependency this `get_current_user`, the scope `"me"` declared at `get_current_active_user` will be included in the `security_scopes.scopes` `list` inside of `get_current_user`. +As the `get_current_active_user` dependency has as a sub-dependency on `get_current_user`, the scope `"me"` declared at `get_current_active_user` will be included in the list of required scopes in the `security_scopes.scopes` passed to `get_current_user`. -And as the *path operation* itself also declares a scope `"items"`, it will also be part of this `list` `security_scopes.scopes` in `get_current_user`. +The *path operation* itself also declares a scope, `"items"`, so this will also be in the list of `security_scopes.scopes` passed to `get_current_user`. Here's how the hierarchy of dependencies and scopes looks like: