about summary refs log tree commit diff
path: root/src/test/rustdoc/inline_local
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-240/+0
2022-09-25rustdoc: update test cases now that code-header is used without in-bandMichael Howell-2/+2
2022-08-13Update `@!has` name in testsNoah Lev-16/+16
2022-08-13Rename `@hastext` to `@hasraw` (same for `matches`)Noah Lev-16/+16
I think `@hasraw` is slightly clearer than `@hastext` since it is actually matching against the raw HTML, not the text nodes.
2022-08-13Update tests: arity-2 `@{has,matches}` -> `...text`Noah Lev-16/+16
2021-12-15rustdoc: remove `--passes` and `--no-defaults`Peter Jaszkowiak-2/+2
- flags no longer function, see #44136 - adjust tests to match new behavior - removed test issue-42875 (covered regression with --no-defaults) - moved input-format to removed flags - move all removed flags to bottom - note flag removal in command help - remove DefaultPassOption enum (now redundant with `show_coverage`)
2021-07-25Rustdoc accessibility: use real headers for doc itemsbors-2/+2
Part of #87059 Partially reverts #84703 Preview at: https://notriddle.com/notriddle-rustdoc-test/real-headers/std/index.html
2021-01-13Update tests for extern block lintingMark Rousskov-2/+2
2020-12-31Fix tests that incorrectly used `!@has` instead of `@!has`Camelid-1/+1
The command is `@!has`, not `!@has`. I don't think these checks were doing anything before! Ideally we would accept `!@has` as well, or at least fail tests that use `!@has`. The current behavior seems to be silently ignoring the check, which is very confusing.
2018-12-25Remove licensesMark Rousskov-102/+1
2018-12-04Add a test case for inlining the docs of a macro reexportGeorg Semmler-0/+28
2018-09-20add more tests for traits-in-non-module-scopeQuietMisdreavus-1/+1
2018-09-20don't check visibility when inlining local implsQuietMisdreavus-0/+28
those get handled properly in strip-hidden anyway
2017-09-30let htmldocck.py check for directoriesQuietMisdreavus-0/+3
2016-11-14rustdoc: Fix some local inlining issuesOliver Middleton-0/+173
* Only inline public items when inlining glob imports. * Never inline while in a private module or a child of a private module. * Never inline impls. This allowed the removal of a workaround in the rendering code.
2016-06-11rustdoc: Don't inline #[doc(hidden)] pub useOliver Middleton-0/+20
Currently if a `#[doc(hidden)] pub use` item is inlined the `hidden` attribute is ignored so the item can appear in the docs. By never inlining such imports, they can be stripped.
2016-03-22Consider `doc(no_inline)` in crate-local inliningmitaa-0/+33
2016-03-10Consider `doc(hidden)` for crate-local inliningmitaa-0/+27
2016-03-09Check for `doc(inline)` instead of `.*(inline)`mitaa-0/+29