openrewrite / openrewrite/rewrite-static-analysis

Assignments should not be redundant

Open
#61 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

recipe
Dominant language
Java
Stars
62
Forks
112
Avg merge
1d 19h
Merged PRs (30d)
40

Description

see: https://rules.sonarsource.com/java/RSPEC-4165

This rule raises an issue when an assignment is useless because the assigned-to variable already holds the value on all execution paths.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked Sonar rule, RSPEC-4165, to understand the redundant-assignment condition. No source file, test, or entry point is named in the issue, so inspect the repository structure for the relevant static-analysis recipe. Done means the rule is identified and handled according to the referenced specification.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.