Results for: "String# "

Inspect a ClassVariableOrWriteNode node.

Inspect a ConstantPathAndWriteNode node.

Inspect a ConstantPathOperatorWriteNode node.

Inspect a ConstantPathOrWriteNode node.

Inspect a GlobalVariableAndWriteNode node.

Inspect a GlobalVariableOperatorWriteNode node.

Inspect a GlobalVariableOrWriteNode node.

Inspect a LocalVariableAndWriteNode node.

Inspect a LocalVariableOperatorWriteNode node.

Inspect a LocalVariableOrWriteNode node.

Copy a ClassVariableAndWriteNode node

Copy a ClassVariableOperatorWriteNode node

Copy a ClassVariableOrWriteNode node

Copy a ConstantPathAndWriteNode node

Copy a ConstantPathOperatorWriteNode node

Copy a ConstantPathOrWriteNode node

Copy a GlobalVariableAndWriteNode node

Copy a GlobalVariableOperatorWriteNode node

Copy a GlobalVariableOrWriteNode node

Copy a LocalVariableAndWriteNode node

Copy a LocalVariableOperatorWriteNode node

Copy a LocalVariableOrWriteNode node

No documentation available

The logical inverse of ‘capture_last_end_same_indent`

When there is an invalid block with an ‘end` missing a keyword right after another `end`, it is unclear where which end is missing the keyword.

Take this example:

class Dog       # 1
    puts "woof" # 2
  end           # 3
end             # 4

the problem line will be identified as:

> end            # 4

This happens because lines 1, 2, and 3 are technically valid code and are expanded first, deemed valid, and hidden. We need to un-hide the matching keyword on line 1. Also work backwards and if there’s a mis-matched end, show it too

Returns debugging information about this node as a string.

Search took: 7ms  ·  Total Results: 4158