🎨 Simplify docs hl_lines ranges and standardize 2 spaces between each range (#1863)

This commit is contained in:
Brock Friedrich
2020-08-29 09:02:58 -05:00
committed by GitHub
parent dfdd371c52
commit be669059fb
79 changed files with 232 additions and 232 deletions

View File

@@ -16,7 +16,7 @@ First, let's create a Pydantic user model.
The same way we use Pydantic to declare bodies, we can use it anywhere else:
```Python hl_lines="5 12 13 14 15 16"
```Python hl_lines="5 12-16"
{!../../../docs_src/security/tutorial002.py!}
```
@@ -38,7 +38,7 @@ The same as we were doing before in the *path operation* directly, our new depen
`get_current_user` will use a (fake) utility function we created, that takes a token as a `str` and returns our Pydantic `User` model:
```Python hl_lines="19 20 21 22 26 27"
```Python hl_lines="19-22 26-27"
{!../../../docs_src/security/tutorial002.py!}
```
@@ -98,7 +98,7 @@ And all of them (or any portion of them that you want) can take the advantage of
And all these thousands of *path operations* can be as small as 3 lines:
```Python hl_lines="30 31 32"
```Python hl_lines="30-32"
{!../../../docs_src/security/tutorial002.py!}
```

View File

@@ -109,7 +109,7 @@ And another utility to verify if a received password matches the hash stored.
And another one to authenticate and return a user.
```Python hl_lines="7 48 55 56 59 60 69 70 71 72 73 74 75"
```Python hl_lines="7 48 55-56 59-60 69-75"
{!../../../docs_src/security/tutorial004.py!}
```
@@ -144,7 +144,7 @@ Define a Pydantic Model that will be used in the token endpoint for the response
Create a utility function to generate a new access token.
```Python hl_lines="6 12 13 14 28 29 30 78 79 80 81 82 83 84 85 86"
```Python hl_lines="6 12-14 28-30 78-86"
{!../../../docs_src/security/tutorial004.py!}
```
@@ -156,7 +156,7 @@ Decode the received token, verify it, and return the current user.
If the token is invalid, return an HTTP error right away.
```Python hl_lines="89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106"
```Python hl_lines="89-106"
{!../../../docs_src/security/tutorial004.py!}
```
@@ -166,7 +166,7 @@ Create a `timedelta` with the expiration time of the token.
Create a real JWT access token and return it.
```Python hl_lines="115 116 117 118 119 120 121 122 123 124 125 126 127 128"
```Python hl_lines="115-128"
{!../../../docs_src/security/tutorial004.py!}
```

View File

@@ -90,7 +90,7 @@ If there is no such user, we return an error saying "incorrect username or passw
For the error, we use the exception `HTTPException`:
```Python hl_lines="3 77 78 79"
```Python hl_lines="3 77-79"
{!../../../docs_src/security/tutorial003.py!}
```
@@ -118,7 +118,7 @@ If your database is stolen, the thief won't have your users' plaintext passwords
So, the thief won't be able to try to use those same passwords in another system (as many users use the same password everywhere, this would be dangerous).
```Python hl_lines="80 81 82 83"
```Python hl_lines="80-83"
{!../../../docs_src/security/tutorial003.py!}
```
@@ -181,7 +181,7 @@ Both of these dependencies will just return an HTTP error if the user doesn't ex
So, in our endpoint, we will only get a user if the user exists, was correctly authenticated, and is active:
```Python hl_lines="58 59 60 61 62 63 64 65 66 67 69 70 71 72 90"
```Python hl_lines="58-67 69-72 90"
{!../../../docs_src/security/tutorial003.py!}
```