rust-lang / rust-lang/rust-analyzer
Move some generic test stuff out of the rust-analyzer crate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Currently regenerating the config, docs and some other stuff require building and running the rust-analyzer crate tests. This is annoying for people contributing fixes just in those places because they'll have to build the entire project and also figure out that they even have to do this in the first place. Additionally, if tidy fails, it will do so after having run all tests on CI which means you are effectively waiting minutes for CI only to realize you forgot a dbg! somewhere later.
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 examining the rust-analyzer crate tests, config and documentation generation, and the tidy checks mentioned in the issue. Determine which generic test work can move out of the crate and how CI currently orders these checks. Done means contributors can regenerate those artifacts without running the full crate tests and tidy failures are reported earlier.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100