-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken documentation links #470
Conversation
@@ -11,7 +11,7 @@ | |||
//! A layer decorates an service and provides additional functionality. It | |||
//! allows other services to be composed with the service that implements layer. | |||
//! | |||
//! A middleware implements the [`Layer`] and [`Service`] trait. | |||
//! A middleware implements the [`Layer`] and [`Service`](tower_service::Service) trait. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This still won't work until https://github.com/rust-lang/rfcs/blob/master/text/1946-intra-rustdoc-links.md is merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this!
I'd prefer it if we could keep the style of link references consistent throughout the docs, but I'm not going to block merging this on that if you have a strong preference for the inline style.
@@ -11,7 +11,7 @@ | |||
//! A layer decorates an service and provides additional functionality. It | |||
//! allows other services to be composed with the service that implements layer. | |||
//! | |||
//! A middleware implements the [`Layer`] and [`Service`] trait. | |||
//! A middleware implements the [`Layer`] and [`Service`](tower_service::Service) trait. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer to put these link references at the end of the doc comment, rather than inline, like
//! A middleware implements the [`Layer`] and [`Service`] trait.
...
//! [`Service`]: tower_service::Service
/// [`MakeService`](crate::make::MakeService) in that it takes service _descriptors_ (see | ||
/// `Target` on `MakeService`) and produces _services_. Since [`Balance`] spreads requests across a | ||
/// _set_ of services, the inner service should produce a [`Discover`], not just a single | ||
/// [`Service`], given a service descriptor. | ||
/// [`Service`](tower_service::Service), given a service descriptor. | ||
/// | ||
/// See the [module-level documentation](..) for details on load balancing. | ||
/// | ||
/// [`Balance`]: crate::balance::p2c::service::Balance | ||
/// [`Discover`]: crate::discover::Discover |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doc comment has a mix of inline and trailing link references. Can we try use one style consistently, please?
I took care of all the broken links while making other docs changes in PR #490, so I'm going to go ahead and close this now. Thanks for working on it, though! |
Fixes
...::make_service::...
links.crate::...