app = FastAPI()
-@app.get('/')
+
+@app.get("/")
def read_root():
- return {'hello': 'world'}
+ return {"Hello": "World"}
+
+
+@app.get("/items/{item_id}")
+def read_item(item_id: int, q: str = None):
+ return {"item_id": item_id, "q": q}
```
+<details markdown="1">
+<summary>Or use <code>async def</code>...</summary>
-Or if your code uses `async` / `await`, use `async def`:
+If your code uses `async` / `await`, use `async def`:
-```Python hl_lines="6"
+```Python hl_lines="7 12"
from fastapi import FastAPI
app = FastAPI()
-@app.get('/')
+
+@app.get("/")
async def read_root():
- return {'hello': 'world'}
+ return {"Hello": "World"}
+
+
+@app.get("/items/{item_id}")
+async def read_item(item_id: int, q: str = None):
+ return {"item_id": item_id, "q": q}
```
-!!! note
- If you don't know, check the _"In a hurry?"_ section about <a href="https://fastapi.tiangolo.com/async/#in-a-hurry" target="_blank">`async` and `await` in the docs</a>.
+**Note**:
+
+If you don't know, check the _"In a hurry?"_ section about <a href="https://fastapi.tiangolo.com/async/#in-a-hurry" target="_blank">`async` and `await` in the docs</a>.
+</details>
* Run the server with:
uvicorn main:app --debug
```
-!!! note
- The command `uvicorn main:app` refers to:
+<details markdown="1">
+<summary>About the command <code>uvicorn main:app --debug</code>...</summary>
+
+The command `uvicorn main:app` refers to:
- * `main`: the file `main.py` (the Python "module").
- * `app`: the object created inside of `main.py` with the line `app = FastAPI()`.
- * `--debug`: make the server restart after code changes. Only do this for development.
+* `main`: the file `main.py` (the Python "module").
+* `app`: the object created inside of `main.py` with the line `app = FastAPI()`.
+* `--debug`: make the server restart after code changes. Only do this for development.
+
+</details>
### Check it
-Open your browser at <a href="http://127.0.0.1:8000" target="_blank">http://127.0.0.1:8000</a>.
+Open your browser at <a href="http://127.0.0.1:8000/items/5?q=somequery" target="_blank">http://127.0.0.1:8000/items/5?q=somequery</a>.
You will see the JSON response as:
```JSON
-{"hello": "world"}
+{"item_id": 5, "q": "somequery"}
```
+You already created an API that:
+
+* Receives HTTP requests in the _paths_ `/` and `/items/{item_id}`.
+* Both _paths_ take `GET` <abbr title="also known as HTTP methods"><em>operations</em></abbr>.
+* The _path_ `/items/{item_id}` has a _path parameter_ `item_id` that should be an `int`.
+* The _path_ `/items/{item_id}` has an optional _query parameter_ `q` that is a `str`.
+
### Interactive API docs
Now go to <a href="http://127.0.0.1:8000/docs" target="_blank">http://127.0.0.1:8000/docs</a>.
## Example upgrade
-Now modify the file `main.py` to include:
+Now modify the file `main.py` to recive a body from a `PUT` request.
-* a path parameter `item_id`.
-* a body, declared using standard Python types (thanks to Pydantic).
-* an optional query parameter `q`.
+Declare the body using standard Python types, thanks to Pydantic.
-```Python hl_lines="2 7 8 9 10 19"
+```Python hl_lines="2 7 8 9 10 24"
from fastapi import FastAPI
from pydantic import BaseModel
is_offer: bool = None
-@app.get('/')
-async def read_root():
- return {'hello': 'world'}
+@app.get("/")
+def read_root():
+ return {"Hello": "World"}
+
+
+@app.get("/items/{item_id}")
+def read_item(item_id: int, q: str = None):
+ return {"item_id": item_id, "q": q}
-@app.post('/items/{item_id}')
-async def create_item(item_id: int, item: Item, q: str = None):
- return {"item_name": item.name, "item_id": item_id, "query": q}
+@app.put("/items/{item_id}")
+def create_item(item_id: int, item: Item):
+ return {"item_name": item.name, "item_id": item_id}
```
The server should reload automatically (because you added `--debug` to the `uvicorn` command above).
Now go to <a href="http://127.0.0.1:8000/docs" target="_blank">http://127.0.0.1:8000/docs</a>.
-* The interactive API documentation will be automatically updated, including the new query, and body:
+* The interactive API documentation will be automatically updated, including the new body:
Coming back to the previous code example, **FastAPI** will:
-* Validate that there is an `item_id` in the path.
-* Validate that the `item_id` is of type `int`.
+* Validate that there is an `item_id` in the path for `GET` and `PUT` requests.
+* Validate that the `item_id` is of type `int` for `GET` and `PUT` requests.
* If it is not, the client will see a useful, clear error.
-* Check if there is an optional query parameter named `q` (as in `http://127.0.0.1:8000/items/foo?q=somequery`).
+* Check if there is an optional query parameter named `q` (as in `http://127.0.0.1:8000/items/foo?q=somequery`) for `GET` requests.
* As the `q` parameter is declared with `= None`, it is optional.
- * Without the `None` it would be required (as is the body).
-* Read the body as JSON:
+ * Without the `None` it would be required (as is the body in the case with `PUT`).
+* For `PUT` requests to `/items/{item_id}`, Read the body as JSON:
* Check that it has a required attribute `name` that should be a `str`.
* Check that is has a required attribute `price` that has to be a `float`.
* Check that it has an optional attribute `is_offer`, that should be a `bool`, if present.
Try changing the line with:
```Python
- return {"item_name": item.name, "item_id": item_id, "query": q}
+ return {"item_name": item.name, "item_id": item_id}
```
...from:
...and see how your editor will auto-complete the attributes and know their types:
+
--- /dev/null
+**Python 3.6+** has support for optional "type hints".
+
+These **"type hints"** are a new syntax (since Python 3.6+) that allow declaring the <abbr title="for example: str, int, float, bool">type</abbr> of a variable.
+
+By declaring types for your variables, editors and tools can give you better support.
+
+This is just a **quick tutorial / refresher** about Python type hints. It covers only the minimum necessary to use them with **FastAPI**... which is actually very little.
+
+**FastAPI** is all based on these type hints, they give it many advantages and benefits.
+
+But even if you never use **FastAPI**, you would benefit from learning a bit about them.
+
+!!! note
+ If you are a Python expert, and you already know everything about type hints, skip to the next chapter.
+
+## Motivation
+
+Let's start with a simple example:
+
+```Python
+{!./src/python_types/tutorial001.py!}
+```
+
+Calling this program outputs:
+
+```
+John Doe
+```
+
+The function does the following:
+
+* Takes a `fist_name` and `last_name`.
+* Converts the first letter of each one to upper case with `title()`.
+* <abbr title="Puts them together, as one. With the contents of one after the other.">Concatenates</abbr> them with a space in the middle.
+
+```Python hl_lines="2"
+{!./src/python_types/tutorial001.py!}
+```
+
+### Edit it
+
+It's a very simple program.
+
+But now imagine that you were writing it from scratch.
+
+At some point you would have started the definition of the function, you had the parameters ready...
+
+But then you have to call "that method that converts the first letter to upper case".
+
+Was it `upper`? Was it `uppercase`? `first_uppercase`? `capitalize`?
+
+Then, you try with the old programer's friend, editor autocompletion.
+
+You type the first parameter of the function, `first_name`, then a dot (`.`) and then hit `Ctrl+Space` to trigger the completion.
+
+But, sadly, you get nothing useful:
+
+<img src="/img/python-types/image01.png">
+
+### Add types
+
+Let's modify a single line from the previous version.
+
+We will change exactly this fragment, the parameters of the function, from:
+
+```Python
+ first_name, last_name
+```
+
+to:
+
+```Python
+ first_name: str, last_name: str
+```
+
+That's it.
+
+Those are the "type hints":
+
+```Python hl_lines="1"
+{!./src/python_types/tutorial002.py!}
+```
+
+That is not the same as declaring default values like would be with:
+
+```Python
+ first_name="john", last_name="doe"
+```
+
+It's a different thing.
+
+We are using colons (`:`), not equals (`=`).
+
+And adding type hints normally doesn't change what happens from what would happen without them.
+
+But now, imagine you are again in the middle of creating that function, but with type hints.
+
+At the same point, you try to trigger the autocomplete with `Ctrl+Space` and you see:
+
+<img src="/img/python-types/image02.png">
+
+With that, you can scroll, seeing the options, until you find the one that "rings a bell":
+
+<img src="/img/python-types/image03.png">
+
+## More motivation
+
+Check this function, it already has type hints:
+
+```Python hl_lines="1"
+{!./src/python_types/tutorial003.py!}
+```
+
+Because the editor knows the types of the variables, you don't only get completion, you also get error checks:
+
+<img src="/img/python-types/image04.png">
+
+Now you know that you have to fix it, convert `age` to a string with `str(age)`:
+
+```Python hl_lines="2"
+{!./src/python_types/tutorial004.py!}
+```
+
+
+## Declaring types
+
+You just saw the main place to declare type hints. As function parameters.
+
+This is also the main place you would use them with **FastAPI**.
+
+### Simple types
+
+You can declare all the standard Python types, not only `str`.
+
+You can use, for example:
+
+* `int`
+* `float`
+* `bool`
+* `bytes`
+
+```Python hl_lines="1"
+{!./src/python_types/tutorial005.py!}
+```
+
+### Types with subtypes
+
+There are some data structures that can contain other values, like `dict`, `list`, `set` and `tuple`. And the internal values can have their own type too.
+
+To declare those types and the subtypes, you can use the standard Python module `typing`.
+
+It exists specifically to support these type hints.
+
+#### Lists
+
+For example, let's define a variable to be a `list` of `str`.
+
+From `typing`, import `List` (with a capital `L`):
+
+```Python hl_lines="1"
+{!./src/python_types/tutorial006.py!}
+```
+
+Declare the variable, with the same colon (`:`) syntax.
+
+As the type, put the `List`.
+
+As the list is a type that takes a "subtype", you put the subtype in square brackets:
+
+```Python hl_lines="4"
+{!./src/python_types/tutorial006.py!}
+```
+
+That means: "the variable `items` is a `list`, and each of the items in this list is a `str`".
+
+By doing that, your editor can provide support even while processing items from the list.
+
+Without types, that's almost impossible to achieve:
+
+<img src="/img/python-types/image05.png">
+
+Notice that the variable `item` is one of the elements in the list `items`.
+
+And still, the editor knows it is a `str`, and provides support for that.
+
+#### Tuples and Sets
+
+You would do the same to declare `tuple`s and `set`s:
+
+```Python hl_lines="1 4"
+{!./src/python_types/tutorial007.py!}
+```
+
+This means:
+
+* The variable `items_t` is a `tuple`, and each of its items is an `int`.
+* The variable `items_s` is a `set`, and each of its items is of type `bytes`.
+
+#### Dicts
+
+To define a `dict`, you pass 2 subtypes, separated by commas.
+
+The first subtype is for the keys of the `dict`.
+
+The second subtype is for the values of the `dict`:
+
+```Python hl_lines="1 4"
+{!./src/python_types/tutorial008.py!}
+```
+
+This means:
+
+* The variable `prices` is a `dict`:
+ * The keys of this `dict` are of type `str` (let's say, the name of each item).
+ * The values of this `dict` are of type `float` (let's say, the price of each item).
+
+
+### Classes as types
+
+You can also declare a class as the type of a variable.
+
+Let's say you have a class `Person`, with a name:
+
+```Python hl_lines="1 2 3"
+{!./src/python_types/tutorial009.py!}
+```
+
+Then you can declare a variable to be of type `Person`:
+
+```Python hl_lines="6"
+{!./src/python_types/tutorial009.py!}
+```
+
+And then, again, you get all the editor support:
+
+<img src="/img/python-types/image06.png">
+
+
+## Pydantic models
+
+<a href="https://pydantic-docs.helpmanual.io/" target="_blank">Pydantic</a> is a Python library to perform data validation.
+
+You declare the "shape" of the data as classes with attributes.
+
+And each attribute has a type.
+
+Then you create an instance of that class with some values and it will validate the values, convert them to the appropriate type (if that's the case) and give you an object with all the data.
+
+And you get all the editor support with that resulting object.
+
+Taken from the official Pydantic docs:
+
+```Python
+{!./src/python_types/tutorial010.py!}
+```
+
+!!! info
+ To learn more about <a href="https://pydantic-docs.helpmanual.io/" target="_blank">Pydantic, check its docs</a>.
+
+**FastAPI** is all based on Pydantic.
+
+You will see a lot more of all this in practice in the <a href="/tutorial/intro/" target="_blank">Tutorial - User Guide</a> (the next section).
+
+
+## Type hints in **FastAPI**
+
+**FastAPI** takes advantage of these type hints to do several things.
+
+With **FastAPI** you declare parameters with type hints and you get:
+
+* **Editor support**.
+* **Type checks**.
+
+...and **FastAPI** uses the same declarations to:
+
+* **Define requirements**: from request path parameters, query parameters, headers, bodies, dependencies, etc.
+* **Convert data**: from the request to the required type.
+* **Validate data**: coming from each request:
+ * Generating **automatic errors** returned to the client when the data is invalid.
+* **Document** the API using OpenAPI:
+ * which is then used by the automatic interactive documentation user interfaces.
+
+This might all sound abstract. Don't worry. You'll see all this in action in the <a href="/tutorial/intro/" target="_blank">Tutorial - User Guide</a> (the next section).
+
+The important thing is that by using standard Python types, in a single place (instead of adding more classes, decorators, etc), **FastAPI** will do a lot of the work for you.
+
+!!! info
+ If you already went through all the tutorial and came back to see more about types, a good resource is <a href="https://mypy.readthedocs.io/en/latest/cheat_sheet_py3.html" target="_blank">the "cheat sheet" from `mypy`</a>.
\ No newline at end of file
projects / thirdparty / fastapi / fastapi.git / commitdiff
