Skip to content

add a workflow to deny on docs issues + fix docs issues #1324

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

iximeow
Copy link
Member

@iximeow iximeow commented May 13, 2025

0b5df8b adds the new workflow and fails because there are a few docs bugs

d1c5a9e fixes the docs bugs. most of it is just references to functions or types by incorrect names/paths. the one interesting one is that HttpResponseContent is not public, but HttpResponseError, which extends it, is. so the only possible implementations of HttpResponseError are ones covered by blanket impls of HttpResponseContent. that seems like a bug, so i've added a pub use HttpResponseContent here too.

the public dropshot::HttpResponseContent then is used in place of the private dropshot::handler::HttpResponseContent in compile errors so that's the changes to bad_endpoint7.stderr.

i'd actually noticed this because ErrorStatusCode has some garbled markdown. it's not exactly a docs error but cargo doc would have complained about the bare URL not being a hyperlink inside <>. that hopefully would have nudged us towards realizing there was a missing [ opening the link. tools work! isn't that neat.

at least, if i've plumbed the env var correctly. i am not an expert yaml
programmer.
@iximeow iximeow force-pushed the ixi/deny-docs-warnings branch from 9ac7d30 to 0b5df8b Compare May 13, 2025 20:05
HttpResponseError is made public at the crate root, but it requires
implementers also implement HttpResponseContent. HttpResponseContent is
*not* public, so implementations of HttpResponseError are constrained to
only being types that are covered by blanket impls of
HttpResponseContent.

i personally don't need to do that, but it makes the docs funky and is
probably an error. it's morally similar to a function returning a type
which is not public.
@iximeow iximeow force-pushed the ixi/deny-docs-warnings branch from efc8ed9 to d1c5a9e Compare May 13, 2025 20:21
@iximeow iximeow marked this pull request as ready for review May 13, 2025 20:28
@iximeow iximeow changed the title add a workflow to check cargo doc and deny on docs issues add a workflow to deny on docs issues + fix docs issues May 13, 2025
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.

1 participant