Uploaded image for project: 'SonarSlang'
  1. SonarSlang
  2. SONARSLANG-172

S1763 should consider more kinds of "jump" statements

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.9
    • Component/s: Ruby, Rules
    • Labels:
      None

      Description

      The implementation of RSPEC-1763 currently only considers:

      • return
      • break
      • continue (Kotlin) / next (Ruby)
      • throw (Kotlin) / raise (Ruby)

      It should also consider:

      • redo (Ruby)
      • retry (Ruby)
      • Ruby break and next with an expression

        Attachments

          Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. SONARSLANG-143 Enable in Ruby rule S1763 (CodeAfterJumpCheck)

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SONARSLANG-91 Support `throw` in S1763 (Dead code after jump)

          • Major - Major loss of function.
          • Closed
          relates to

          Bug Detection - RSPEC-1763 All code should be reachable

          • Active

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                pierre-yves.nicolas Pierre-Yves Nicolas
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: