mirror of
https://github.com/actix/actix-web.git
synced 2024-11-23 01:51:11 +00:00
docs: fix Data doc
This commit is contained in:
parent
215a52f565
commit
a7983351be
2 changed files with 8 additions and 10 deletions
14
.github/dependabot.yml
vendored
14
.github/dependabot.yml
vendored
|
@ -1,12 +1,10 @@
|
||||||
version: 2
|
version: 2
|
||||||
updates:
|
updates:
|
||||||
- package-ecosystem: "cargo"
|
- package-ecosystem: cargo
|
||||||
directory: "/"
|
directory: /
|
||||||
schedule:
|
schedule:
|
||||||
interval: "monthly"
|
interval: weekly
|
||||||
open-pull-requests-limit: 10
|
- package-ecosystem: github-actions
|
||||||
- package-ecosystem: "github-actions"
|
directory: /
|
||||||
directory: "/"
|
|
||||||
schedule:
|
schedule:
|
||||||
interval: "monthly"
|
interval: daily
|
||||||
open-pull-requests-limit: 10
|
|
||||||
|
|
|
@ -32,8 +32,8 @@ pub(crate) type FnDataFactory =
|
||||||
/// Since the Actix Web router layers application data, the returned object will reference the
|
/// Since the Actix Web router layers application data, the returned object will reference the
|
||||||
/// "closest" instance of the type. For example, if an `App` stores a `u32`, a nested `Scope`
|
/// "closest" instance of the type. For example, if an `App` stores a `u32`, a nested `Scope`
|
||||||
/// also stores a `u32`, and the delegated request handler falls within that `Scope`, then
|
/// also stores a `u32`, and the delegated request handler falls within that `Scope`, then
|
||||||
/// extracting a `web::<Data<u32>>` for that handler will return the `Scope`'s instance.
|
/// extracting a `web::Data<u32>` for that handler will return the `Scope`'s instance. However,
|
||||||
/// However, using the same router set up and a request that does not get captured by the `Scope`,
|
/// using the same router set up and a request that does not get captured by the `Scope`,
|
||||||
/// `web::<Data<u32>>` would return the `App`'s instance.
|
/// `web::<Data<u32>>` would return the `App`'s instance.
|
||||||
///
|
///
|
||||||
/// If route data is not set for a handler, using `Data<T>` extractor would cause a `500 Internal
|
/// If route data is not set for a handler, using `Data<T>` extractor would cause a `500 Internal
|
||||||
|
|
Loading…
Reference in a new issue