about summary refs log tree commit diff
path: root/src/librustdoc/html
AgeCommit message (Collapse)AuthorLines
2022-05-25Add new eslint rule "comma-dangle"Guillaume Gomez-0/+1
2022-05-25Add new eslint rule "space-before-blocks"Guillaume Gomez-0/+1
2022-05-25Add new eslint rule "space-before-function-paren"Guillaume Gomez-7/+8
2022-05-25Add eslint rule "space-infix-ops"Guillaume Gomez-0/+1
2022-05-25Auto merge of #97365 - klensy:rustdoc-vs-clippy, r=notriddlebors-39/+44
rustdoc: fix few clippy lints Fix few clippy lints: second commit - perf ones, first - other ones.
2022-05-25Rollup merge of #97355 - GuillaumeGomez:remove-brush, r=Dylan-DPCYuki Okushi-1/+0
Remove unused brush image r? `@notriddle`
2022-05-24fix clippy perf lintsklensy-15/+23
2022-05-24fix simple clippy lintsklensy-24/+21
2022-05-24Remove unused brush imageGuillaume Gomez-1/+0
2022-05-24Allow to click on toggle text to update itGuillaume Gomez-36/+39
2022-05-23Auto merge of #94053 - GuillaumeGomez:fields-stripped, r=notriddlebors-11/+11
rustdoc: Remove fields_stripped fields (and equivalents) Fixes #90588. r? `@camelid`
2022-05-23Rollup merge of #97286 - GuillaumeGomez:eslint-check-fn, r=notriddleDylan DPC-0/+1
Add new eslint rule to prevent whitespace before function call paren It prevents `foo ()` basically. :) r? `@notriddle`
2022-05-23Auto merge of #97195 - notriddle:notriddle/cleanup, r=GuillaumeGomezbors-3/+3
rustdoc: shrink GenericArgs/PathSegment with boxed slices This PR also contains a few cleanup bits and pieces, but one of them is a broken intra-doc link, and the other is removing an unused Hash impl. The last commit is the one that matters.
2022-05-22Clean up `&args[..]`, use more readable `args.iter()` insteadMichael Howell-3/+3
2022-05-22Add new eslint rule to prevent whitespace before function call parenGuillaume Gomez-0/+1
2022-05-22Auto merge of #97177 - oli-obk:const-stability, r=davidtwcobors-4/+1
Implement proper stability check for const impl Trait, fall back to unstable const when undeclared Continuation of #93960 `@jhpratt` it looks to me like the test was simply not testing for the failure you were looking for? Your checks actually do the right thing for const traits?
2022-05-21Shrink GenericArgs/PathSegment with boxed slicesMichael Howell-3/+3
2022-05-21Auto merge of #97246 - GuillaumeGomez:rollup-btcok8x, r=GuillaumeGomezbors-0/+8
Rollup of 7 pull requests Successful merges: - #97190 (Add implicit call to from_str via parse in documentation) - #97218 (Add eslint checks) - #97219 (make ptr::invalid not the same as a regular int2ptr cast) - #97223 (Remove quadratic behaviour from -Zunpretty=hir-tree.) - #97232 (typo) - #97237 (Add some more weird-exprs) - #97238 (Bump LLVM fetched from CI to fix run-make) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
2022-05-21Remove fields_stripped fields (and equivalents)Guillaume Gomez-11/+11
2022-05-21Rollup merge of #97218 - GuillaumeGomez:eslint-checks, r=notriddleGuillaume Gomez-0/+8
Add eslint checks The first check is to ensure that `=>` is always surrounded with whitespaces. The second is to ensure that the dict objects looks like this: `{"a": 2}` and not `{"a" : 2}` or `{"a":2}`. r? ``@notriddle``
2022-05-21Auto merge of #93963 - GuillaumeGomez:reduce-clean-type-size, r=notriddlebors-5/+1
rustdoc: Reduce clean::Type size There is no need to keep the `DefId` around since it's allow used to compute if we should show a cast or not. As such, we can simply directly store the boolean. I think it's not what you had in mind `@camelid` but I guess it's still an improvement? :wink: It was discussed in https://github.com/rust-lang/rust/pull/93941. r? `@camelid`
2022-05-21Remove `crate` visibility modifier in libs, testsJacob Pratt-245/+263
2022-05-20Add eslint key-spacing checkGuillaume Gomez-0/+4
2022-05-20Add eslint arrow-spacing checkGuillaume Gomez-0/+4
2022-05-19Add new lint to enforce whitespace after keywordsGuillaume Gomez-2/+6
2022-05-19Add and use stability helper methodsJacob Pratt-4/+1
This avoids an ambiguity (when reading) where `.level.is_stable()` is not immediately clear whether it is general stability or const stability.
2022-05-18Move some DOM generation into the HTML settings file directlyGuillaume Gomez-19/+15
2022-05-18Rollup merge of #97113 - GuillaumeGomez:search-ui-fixes, r=notriddleYuki Okushi-8/+8
Search GUI fixes The first fix is about the duplicated "in": ![Screenshot from 2022-05-17 13-25-53](https://user-images.githubusercontent.com/3050060/168814186-a4e9064f-4325-469c-8bf6-46ea2737a24f.png) The second fix is about the `<select>` broken style: ![Screenshot from 2022-05-17 13-37-03](https://user-images.githubusercontent.com/3050060/168814182-b1c5ae66-d8cf-4fd5-a227-5aa8cd8453ab.png) ![Screenshot from 2022-05-17 13-36-55](https://user-images.githubusercontent.com/3050060/168814184-be9e56f8-fad4-477c-899e-9abff4d4910c.png) You can test it [here](https://rustdoc.crud.net/imperio/search-ui-fixes/doc/foo/index.html?search=test). r? `@notriddle`
2022-05-17rustdoc: make search.js a moduleJacob Hoffman-Andrews-52/+73
Previously, search.js relied on the DOM and the `window` object. It can now be loaded in the absence of the DOM, for instance by Node. The same is true of search-index.js. This allows removing a lot of code from src/tools/rustdoc-js/tester.js that tried to parse search.js and extract specific functions that were needed for testing.
2022-05-17Fix display of search crate filter selectGuillaume Gomez-7/+7
2022-05-17Fix duplicated "in" in the search result textGuillaume Gomez-1/+1
2022-05-15Add new eslint rule about brace styleGuillaume Gomez-33/+57
2022-05-15Reduce clean::Type size by replacing a DefId (only used to check for ↵Guillaume Gomez-5/+1
display) with a boolean
2022-05-14Remove theme picker buttonGuillaume Gomez-199/+12
2022-05-14Improve settings menu displayGuillaume Gomez-31/+110
2022-05-14Rollup merge of #96998 - notriddle:notriddle/var-N, r=jshaYuki Okushi-1/+1
rustdoc: remove weird, unused variable from source-files.js
2022-05-12rustdoc: remove weird, unused variable from source-files.jsMichael Howell-1/+1
2022-05-12rustdoc: fix GUI crash when searching for magic JS property valuesMichael Howell-2/+2
2022-05-12Auto merge of #96974 - matthiaskrgr:rollup-jd4otnc, r=matthiaskrgrbors-39/+5
Rollup of 5 pull requests Successful merges: - #95896 (Note the contacts for the nvptx64 target(s)) - #96860 (openbsd: convert futex timeout managment to Timespec usage) - #96939 (Fix settings page CSS) - #96941 (update graphviz links) - #96968 (Add tests for #96806) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
2022-05-12Rollup merge of #96939 - GuillaumeGomez:settings-css, r=notriddleMatthias Krüger-39/+5
Fix settings page CSS In https://github.com/rust-lang/rust/pull/96741, I moved the CSS loading outside of `settings.js`. The result was that on the settings page, there isn't the settings CSS anymore: ![Screenshot from 2022-05-11 11-09-24](https://user-images.githubusercontent.com/3050060/167817969-6750931b-3e6e-4178-b5a9-ee3851e983be.png) I also used this opportunity to remove unused CSS rules (we don't have `<select>` elements anymore in the settings). cc `@jsha` r? `@notriddle`
2022-05-12Auto merge of #95562 - lcnr:attr-no-encode, r=davidtwcobors-1/+1
don't encode only locally used attrs Part of https://github.com/rust-lang/compiler-team/issues/505. We now filter builtin attributes before encoding them in the crate metadata in case they should only be used in the local crate. To prevent accidental misuse `get_attrs` now requires the caller to state which attribute they are interested in. For places where that isn't trivially possible, I've added a method `fn get_attrs_unchecked` which I intend to remove in a followup PR. After this pull request landed, we can then slowly move all attributes to only be used in the local crate while being certain that we don't accidentally try to access them from extern crates. cc https://github.com/rust-lang/rust/pull/94963#issuecomment-1082924289
2022-05-11Remove unused CSS settings rulesGuillaume Gomez-36/+0
2022-05-11Add missing CSS file for settings pageGuillaume Gomez-3/+5
2022-05-11Rollup merge of #96900 - GuillaumeGomez:fix-js-error, r=notriddleYuki Okushi-3/+1
Fix js error On the source code pages, we get a JS error: ![Screenshot from 2022-05-10 16-26-53](https://user-images.githubusercontent.com/3050060/167656292-51e0b0e9-6b0c-4f94-82e0-dd8fb77adf52.png) It's fixed in the first commit. The second one is removing an unused CSS rule and the third one is a little cleanup of a GUI test. cc ``@jsha`` r? ``@notriddle``
2022-05-11Rollup merge of #96879 - notriddle:notriddle/search-ranking, r=GuillaumeGomezYuki Okushi-1/+1
rustdoc: search result ranking fix # Before ![image](https://user-images.githubusercontent.com/1593513/167477286-91049761-67f9-4a73-8fb7-09dbb19ca76c.png) # After ![image](https://user-images.githubusercontent.com/1593513/167477345-6733bc0f-4bb2-4625-9f7f-094031e36414.png)
2022-05-10Remove unused CSS ruleGuillaume Gomez-1/+0
2022-05-10Fix JS error in source code pagesGuillaume Gomez-2/+1
2022-05-10update rustdoclcnr-1/+1
2022-05-09rustdoc: search result ranking fixMichael Howell-1/+1
2022-05-09Rollup merge of #96858 - notriddle:notriddle/cleanup-search-js, r=GuillaumeGomezMatthias Krüger-2/+2
Remove unused param from search.js::checkPath