about summary refs log tree commit diff
path: root/tests/rustdoc-ui/intra-doc
AgeCommit message (Collapse)AuthorLines
2023-11-24Bless rustdoc-ui testsNilstrieb-16/+16
Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-10-05Add a note to duplicate diagnosticsAlex Macleod-0/+1
2023-07-22add tests for broken links in unused doc stringsLukas Markeffsky-0/+43
2023-05-26rustdoc: get unnormalized link destination for suggestionsMichael Howell-3/+416
Fixes #110111 This bug, and the workaround in this commit, is closely linked to [raphlinus/pulldown-cmark#441], getting offsets of link components. In particular, pulldown-cmark doesn't provide the offsets of the contents of a link. To work around this, rustdoc parser parts of a link definition itself. [raphlinus/pulldown-cmark#441]: https://github.com/raphlinus/pulldown-cmark/issues/441
2023-05-23Add regression test for #111189Guillaume Gomez-0/+31
2023-04-29move lint tests into subdirectoriesjyn-0/+159
2023-04-29Move some rustdoc-ui tests to subdirectoriesjyn-0/+19
2023-04-26Rollup merge of #110329 - aDotInTheVoid:json-inline-again, r=jyn514jyn-11/+0
Improve tests for #110138 These should live in rustdoc-json, not rustdoc-ui, so we can run assertions, and not just check there's no ICE CC #100515, as we never document this suite r? rustdoc
2023-04-18rustdoc: fix ICE from rustc_resolve and librustdoc parse divergenceMichael Howell-0/+60
2023-04-14Move test from rustdoc-ui to rustdoc-jsonAlona Enraght-Moony-11/+0
2023-04-10fix(doc): do not parse inline when output is json for external cratebohan-0/+11
2023-04-05Bless rustdoc-ui test with new errors orderRémy Rakic-15/+15
The order in which the multiple errors for the ambiguous intra doc links are printed is different.
2023-03-31Rollup merge of #109104 - ↵Guillaume Gomez-47/+460
GuillaumeGomez:fix-invalid-suggestion-ambiguous-intra-doc2, r=oli-obk,notriddle rustdoc: Fix invalid suggestions on ambiguous intra doc links v2 Fixes https://github.com/rust-lang/rust/issues/108653. This is another approach to fixing the same issue. This time, we keep the computed information around instead of re-computing it. Strangely enough, the order for ambiguities seem to have been changed. Not an issue but it creates a lot of diff... So which version do you prefer? r? `@notriddle`
2023-03-24Put back `is_derive_trait_collision` checkGuillaume Gomez-0/+22
2023-03-24Update UI tests for primitive type ambiguity error renamingGuillaume Gomez-25/+25
2023-03-24Add regression tests for #108653Guillaume Gomez-25/+416
2023-03-23rustdoc: Skip doc link resolution for non-exported itemsVadim Petrochenkov-0/+13
2023-03-21rustdoc: Cleanup parent module tracking for doc linksVadim Petrochenkov-0/+11
Keep ids of the documented items themselves, not their parent modules. Parent modules can be retreived from those ids when necessary.
2023-03-17rustdoc: Correctly merge import's and its target's docs in one more caseVadim Petrochenkov-0/+16
2023-02-20Make `configure_and_expand` "infalllible" by just aborting the compilation ↵Oli Scherer-3/+1
if it fails instead of bubbling out an error
2023-02-19Rollup merge of #107951 - petrochenkov:procmacdoc, r=jackh726Dylan DPC-0/+27
resolve: Fix doc links referring to other crates when documenting proc macro crates directly Fixes https://github.com/rust-lang/rust/issues/107950
2023-02-18rustdoc: Cleanup broken link callbacksVadim Petrochenkov-16/+16
2023-02-13resolve: Fix doc links referring to other crates when documenting proc macro ↵Vadim Petrochenkov-0/+27
crates directly
2023-02-11rustdoc: Don't resolve link to field on different variantclubby789-1/+29
2023-01-11Move /src/test to /testsAlbert Larsan-0/+2133