Compare commits

...

2 Commits

Author SHA1 Message Date
github-actions bcb8e64f67 📝 Update release notes 2024-06-01 21:06:19 +00:00
Alejandra 256426ede1
📝 Update note in `path-params-numeric-validations.md` (#11672) 2024-06-01 16:05:52 -05:00
2 changed files with 2 additions and 5 deletions

View File

@ -15,6 +15,7 @@ hide:
### Docs
* 📝 Update note in `path-params-numeric-validations.md`. PR [#11672](https://github.com/tiangolo/fastapi/pull/11672) by [@alejsdev](https://github.com/alejsdev).
* 📝 Tweak intro docs about `Annotated` and `Query()` params. PR [#11664](https://github.com/tiangolo/fastapi/pull/11664) by [@tiangolo](https://github.com/tiangolo).
* 📝 Update JWT auth documentation to use PyJWT instead of pyhon-jose. PR [#11589](https://github.com/tiangolo/fastapi/pull/11589) by [@estebanx64](https://github.com/estebanx64).
* 📝 Update docs. PR [#11603](https://github.com/tiangolo/fastapi/pull/11603) by [@alejsdev](https://github.com/alejsdev).

View File

@ -92,11 +92,7 @@ For example, to declare a `title` metadata value for the path parameter `item_id
```
!!! note
A path parameter is always required as it has to be part of the path.
So, you should declare it with `...` to mark it as required.
Nevertheless, even if you declared it with `None` or set a default value, it would not affect anything, it would still be always required.
A path parameter is always required as it has to be part of the path. Even if you declared it with `None` or set a default value, it would not affect anything, it would still be always required.
## Order the parameters as you need