Using ruby 2.7.x, if I create a syntax error, rubocop reports it at the end of the file:
Inspecting 1 file
E
Offenses:
config.ru:179:1: E: Lint/Syntax: unexpected token $end
(Using Ruby 2.7 parser; configure using TargetRubyVersion parameter, under AllCops)
1 file inspected, 1 offense detected
However, the error was introduced in a previous line.
This means that if we're running rubocop directly, we would see that this file is not parseable, but using pronto there's no complaints (this flies under the radar in a CI check, for instance).
Would it make sense that pronto always reports Syntax errors on touched files, even outside of the patch zone?
Using ruby 2.7.x, if I create a syntax error, rubocop reports it at the end of the file:
However, the error was introduced in a previous line.
This means that if we're running rubocop directly, we would see that this file is not parseable, but using pronto there's no complaints (this flies under the radar in a CI check, for instance).
Would it make sense that pronto always reports Syntax errors on touched files, even outside of the patch zone?