diff options
| author | bors <bors@rust-lang.org> | 2022-05-17 19:50:44 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-05-17 19:50:44 +0000 |
| commit | 4c5f6e6277b89e47d73a192078697f7a5f3dc0ac (patch) | |
| tree | cb9f25573854a972477dd395dbe83908ec1260d2 /compiler/rustc_codegen_llvm/src | |
| parent | 00755e4ca68f12ed200e921276788ab19975e85f (diff) | |
| parent | 453979462a2cba1c32b61f96a18c125805827291 (diff) | |
| download | rust-4c5f6e6277b89e47d73a192078697f7a5f3dc0ac.tar.gz rust-4c5f6e6277b89e47d73a192078697f7a5f3dc0ac.zip | |
Auto merge of #92570 - jsha:rustdoc-search-refactor, r=GuillaumeGomez
Simplify rustdoc search test Previously, rustdoc search attempted to parse search.js and extract out only certain methods and variables. This change makes search.js and search-index.js loadable as [CommonJS modules](https://nodejs.org/api/modules.html#modules-commonjs-modules), so they can be loaded directly. As part of that change, I had to separate execSearch from interacting with the DOM. This wound up being a nice cleanup that made more explicit what inputs it was taking. I removed search.js' dependency on storage.js by moving hasOwnPropertyRustdoc directly into search.js, and replacing onEach with forEach in a path that is called by the tester. r? `@GuillaumeGomez` Demo: https://rustdoc.crud.net/jsha/rustdoc-search-refactor/std/?search=foo
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
