Fix/rustdoc warnings#2045#2084
Conversation
|
Made suggested changes. Please check. |
|
Thank you for applying my suggestions, all changes look good now. However, in the current state the PR does not fix the mentioned issue so there are still things to do.
As a side-note I feel like the current PR description doesn't really help. It's really verbose and contains repeated content from my contents as well as confusing parts (e.g. |
|
@katrinafyi now addressed the comment I referenced previously with caa7d5c. Consequently I've updated my above comment. I recommend you to now rebase this PR on master, so that you can test the changes with this new commit included. You can then remove the line with |
|
@krishnakurtakoti, can you rebase this branch on top of |
- Use plain backticks for private intra-doc link `Chain::traverse`. - Fully qualify `crate::ResolvedInputSource::Stdin` in `BaseInfo` doc. - Wrap CLI/shell examples in `text`/`bash` fenced code blocks so rustdoc does not try to parse them as Rust. - Drop `continue-on-error` from the rustdoc CI step and pass `RUSTDOCFLAGS=-D warnings` so future warnings fail the build.
dbb0806 to
9f5d42d
Compare
52ff44e to
9df37c5
Compare
mre
left a comment
There was a problem hiding this comment.
Thanks for your contribution @krishnakurtakoti.
I went ahead and fixed the remaining issues.
Will merge this as the changes should be uncontroversial as they only fix lints.
Fixes issues/2045