add a workflow to deny on docs issues + fix docs issues #1324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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, butHttpResponseError
, which extends it, is. so the only possible implementations ofHttpResponseError
are ones covered by blanket impls ofHttpResponseContent
. that seems like a bug, so i've added apub use HttpResponseContent
here too.the public
dropshot::HttpResponseContent
then is used in place of the privatedropshot::handler::HttpResponseContent
in compile errors so that's the changes tobad_endpoint7.stderr
.i'd actually noticed this because
ErrorStatusCode
has some garbled markdown. it's not exactly a docs error butcargo 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.