rwf2
/
Rocket
mirror of https://github.com/rwf2/Rocket.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix several broken rustdoc links.

This commit is contained in:
Sergio Benitez 2023-03-23 10:23:56 -07:00
parent 322f88e61a
commit 1edfa15d52
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
core/codegen/src/lib.rs
View File

@ -1061,9 +1061,9 @@ pub fn derive_uri_display_path(input: TokenStream) -> TokenStream {
emit!(derive::uri_display::derive_uri_display_path(input)) emit!(derive::uri_display::derive_uri_display_path(input))
} }
/// Generates a [`Vec`] of [`Route`]s from a set of route paths. /// Generates a `Vec` of [`Route`]s from a set of route paths.
/// ///
/// The `routes!` macro expands a list of route paths into a [`Vec`] of their /// The `routes!` macro expands a list of route paths into a `Vec` of their
/// corresponding [`Route`] structures. For example, given the following routes: /// corresponding [`Route`] structures. For example, given the following routes:
/// ///
/// ```rust /// ```rust
@ -1117,9 +1117,9 @@ pub fn routes(input: TokenStream) -> TokenStream {
emit!(bang::routes_macro(input)) emit!(bang::routes_macro(input))
} }
/// Generates a [`Vec`] of [`Catcher`]s from a set of catcher paths. /// Generates a `Vec` of [`Catcher`]s from a set of catcher paths.
/// ///
/// The `catchers!` macro expands a list of catcher paths into a [`Vec`] of /// The `catchers!` macro expands a list of catcher paths into a `Vec` of
/// their corresponding [`Catcher`] structures. For example, given the following /// their corresponding [`Catcher`] structures. For example, given the following
/// catchers: /// catchers:
/// ///

6
core/lib/src/request/request.rs
View File

@ -308,7 +308,7 @@ impl<'r> Request<'r> {
/// Because it is common for proxies to forward connections for clients, the /// Because it is common for proxies to forward connections for clients, the
/// remote address may contain information about the proxy instead of the /// remote address may contain information about the proxy instead of the
/// client. For this reason, proxies typically set a "X-Real-IP" header /// client. For this reason, proxies typically set a "X-Real-IP" header
/// [`ip_header`](rocket::Config::ip_header) with the client's true IP. To /// [`ip_header`](crate::Config::ip_header) with the client's true IP. To
/// extract this IP from the request, use the [`real_ip()`] or /// extract this IP from the request, use the [`real_ip()`] or
/// [`client_ip()`] methods. /// [`client_ip()`] methods.
/// ///
@ -358,7 +358,7 @@ impl<'r> Request<'r> {
} }
/// Returns the IP address of the configured /// Returns the IP address of the configured
/// [`ip_header`](rocket::Config::ip_header) of the request if such a header /// [`ip_header`](crate::Config::ip_header) of the request if such a header
/// is configured, exists and contains a valid IP address. /// is configured, exists and contains a valid IP address.
/// ///
/// # Example /// # Example
@ -387,7 +387,7 @@ impl<'r> Request<'r> {
} }
/// Attempts to return the client's IP address by first inspecting the /// Attempts to return the client's IP address by first inspecting the
/// [`ip_header`](rocket::Config::ip_header) and then using the remote /// [`ip_header`](crate::Config::ip_header) and then using the remote
/// connection's IP address. Note that the built-in `IpAddr` request guard /// connection's IP address. Note that the built-in `IpAddr` request guard
/// can be used to retrieve the same information in a handler: /// can be used to retrieve the same information in a handler:
/// ///