clean up and unify logic used by `rustdoc-js` and `rustdoc-js-std` test suites.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
I cannot find the code that actually runs rustdoc on the rustdoc-js/*.rs files, and for some unknown reason, that code is not actually getting run (leading to issues about search-index.js not being found).
This code is quite a mess, rustdoc-js-std seems to be mostly implemented in bootstrap, while rustdoc-js is mostly implemented in compiletest.
This discrepancy leads to an ever increasing number of discrepancies between the exact behavior of the two test suites. Rather than trying to patch these up one by one, I would rather we take a big picture approach.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the code that runs rustdoc for the rustdoc-js/*.rs files, then compare the rustdoc-js and rustdoc-js-std test-suite implementations in compiletest and bootstrap. Investigate why search-index.js is not found and map the behavioral discrepancies. Done means the two suites use unified logic rather than accumulating separate fixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, compilers, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100