openrewrite / openrewrite/rewrite-static-analysis
RSPEC-4034 - "Stream" call chains should be simplified when possible
Open
Nobody has claimed this yet.
recipe
- Dominant language
- Java
- Stars
- 62
- Forks
- 112
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 40
Description
private static boolean isTypeAllowed(String type) {
return Set.of("types").stream().filter(type::contains).collect(Collectors.toList()).isEmpty();
}
private static boolean isTypeAllowed(String type) {
return Set.of("types").stream().stream().filter(type::contains).count() == 0
}
private static boolean isTypeAllowed(String type) {
return Set.of("types").stream().noneMatch(type::contains);
}
More examples : https://rules.sonarsource.com/java/RSPEC-4034
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 reviewing the RSPEC-4034 examples in the issue and the linked Sonar rule, then inspect the repository's existing Java static-analysis recipes and tests for the entry point used to detect stream call chains. Done means the applicable chains are simplified to equivalent terminal operations and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100