Since commit 41ee55b8c50d95175cfb3cb8cb530f09e61ccf7c all occurences of TStrings are ignored after a bitwise or "|". I think it is caused by the exclusion of block parameters with the process_on_op method and the early return in process_on_ident. Both, block parameter limiters and the bitwise or operator, are recoognized as :on_op by the Ripper Lexer.
Here is a dummy example to demonstrate the problem:
test_file.rb:
[1, 2].map do |e|
puts _('tstring1')
result = e | 2
puts _('tstring2')
result
end
Since commit 41ee55b8c50d95175cfb3cb8cb530f09e61ccf7c all occurences of TStrings are ignored after a bitwise or "|". I think it is caused by the exclusion of block parameters with the
process_on_op
method and the early return inprocess_on_ident
. Both, block parameter limiters and the bitwise or operator, are recoognized as:on_op
by the Ripper Lexer.Here is a dummy example to demonstrate the problem:
test_file.rb:
Even though I would expect an output like this: