openrewrite / openrewrite/rewrite
Validate in the testing framework that we're not loading any deprecated recipes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.7k
- Forks
- 570
- Avg merge
- 13h 12m
- Merged PRs (30d)
- 261
Description
What problem are you trying to solve?
Sometimes we deprecate recipes, as seen here
In those cases we want to alert folks downstream by failing tests that use those deprecated recipes. That ought to then show up when they bump dependency versions, to speed up the migration off of deprecated recipes
Have you considered any alternatives or workarounds?
We could warn, but then those warnings get lost in the output.
We could warn/fail in main, but that's a little over eager.
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 testing framework's recipe-loading path and the tests that execute recipes. Trace how deprecated recipes are identified, then define the test-only failure point so downstream tests fail when they use one while normal execution remains unchanged. Done means deprecated recipe usage fails clearly during framework tests and existing non-deprecated tests still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100