From adf4e77dd6e939db7afc895ad318e0452fb9ea51 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebasti=C3=A1n=20Ram=C3=ADrez?= Date: Thu, 1 Sep 2022 11:05:41 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Add=20tip=20about=20using=20alia?= =?UTF-8?q?s=20for=20form=20data=20fields=20(#5329)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/en/docs/tutorial/request-forms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/docs/tutorial/request-forms.md b/docs/en/docs/tutorial/request-forms.md index 2021a098f..26922685a 100644 --- a/docs/en/docs/tutorial/request-forms.md +++ b/docs/en/docs/tutorial/request-forms.md @@ -27,7 +27,7 @@ For example, in one of the ways the OAuth2 specification can be used (called "pa The spec requires the fields to be exactly named `username` and `password`, and to be sent as form fields, not JSON. -With `Form` you can declare the same metadata and validation as with `Body` (and `Query`, `Path`, `Cookie`). +With `Form` you can declare the same configurations as with `Body` (and `Query`, `Path`, `Cookie`), including validation, examples, an alias (e.g. `user-name` instead of `username`), etc. !!! info `Form` is a class that inherits directly from `Body`.