Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

hlb8122
Copy link
Contributor

@hlb8122 hlb8122 commented Sep 21, 2020

Fixes

  • Fix ...::make_service::... links.
  • Replace links with root given explicitly by crate::...

@@ -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.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hlb8122 hlb8122 marked this pull request as ready for review September 25, 2020 16:44
Copy link
Member

@hawkw hawkw left a 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.
Copy link
Member

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

Comment on lines +11 to +19
/// [`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
Copy link
Member

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?

@hawkw hawkw added this to the v0.4 milestone Dec 29, 2020
@hawkw
Copy link
Member

hawkw commented Jan 7, 2021

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!

@hawkw hawkw closed this Jan 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants