Browse Source

docs: clarify required query params that can represent None

pull/14750/head
Alberto Zambrano 6 months ago
parent
commit
22bfbbc08f
  1. 4
      docs/en/docs/tutorial/query-params-str-validations.md

4
docs/en/docs/tutorial/query-params-str-validations.md

@ -251,9 +251,7 @@ This forces clients to send a value, even if the value represents `None`.
To do that, you can declare that `None` is a valid type but simply do not declare a default value. To do that, you can declare that `None` is a valid type but simply do not declare a default value.
Query parameters are always received as strings, so clients cannot send an actual Query parameters are always received as strings, so clients cannot send an actual `None` value directly. If needed, you must explicitly handle a string representation (for example, `"null"`) and convert it to `None` inside your application logic.
`None` value directly. If needed, you must explicitly handle a string representation
(for example, `"null"`) and convert it to `None` inside your application logic.
{* ../../docs_src/query_params_str_validations/tutorial006c_an_py310.py hl[9] *} {* ../../docs_src/query_params_str_validations/tutorial006c_an_py310.py hl[9] *}

Loading…
Cancel
Save