From: cirrusj Date: Sat, 27 Aug 2022 21:00:09 +0000 (+0300) Subject: ✏ Fix typos in `docs/tutorial/fastapi/update.md` (#268) X-Git-Tag: 0.0.7~47 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=452f18d8bc91e66ce43802b86b26b15a109bb9f7;p=thirdparty%2Ffastapi%2Fsqlmodel.git ✏ Fix typos in `docs/tutorial/fastapi/update.md` (#268) Co-authored-by: Sebastián Ramírez --- diff --git a/docs/tutorial/fastapi/update.md b/docs/tutorial/fastapi/update.md index e08f169b..b845d5a2 100644 --- a/docs/tutorial/fastapi/update.md +++ b/docs/tutorial/fastapi/update.md @@ -218,11 +218,11 @@ And when getting the data with `hero.dict(exclude_unset=True)`, we would get: } ``` -So, we would use that value and upate the `age` to `None` in the database, **just as the client intended**. +So, we would use that value and update the `age` to `None` in the database, **just as the client intended**. Notice that `age` here is `None`, and **we still detected it**. -Also that `name` was not even sent, and we don't *accidentally* set it to `None` or something, we just didn't touch it, because the client didn't send it, so we are **perfectly fine**, even in these corner cases. ✨ +Also that `name` was not even sent, and we don't *accidentally* set it to `None` or something, we just didn't touch it, because the client didn't sent it, so we are **perfectly fine**, even in these corner cases. ✨ These are some of the advantages of Pydantic, that we can use with SQLModel. 🎉