Executable outputs warnnings

[smarquez1]

Running erblint --format I'm getting warnings that make my editor (neovim / none-ls) fail to read the outputted diagnostics.

This might be something that needs to be addressed by my editor plugin, but I just wanted to raise the issue

warning: parser/current is loading parser/ruby33, which recognizes 3.3.3-compliant syntax, but you are running 3.3.0.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
{"metadata":{"erb_lint_version":"0.5.0","ruby_engine":"ruby","ruby_version":"3.3.0","ruby_patchlevel":"0","ruby_...

[thomaswitt]

I have the same problem. This makes erb_lint unusable as a linter inside neovim as this is not parsable by the Autocorrector. There needs to be a config.yaml option to suppress these warnings. This will now be a more widespread problem as Ruby 3.4 is officially released. I know that whitequark produces this error, but erb_lint should suppress it via a config option.

[etiennebarrie]

The parser gem emits its warning to stderr. Usually other programs like editors are good about only using the output of stdout. For example, it seems that none-ls's generator_factory helper has a ignore_stderr option.

I've created #393 to make sure we only output the autocorrected file to stdout, everything else (including the parser gem warning) go to stderr, and this should make it usable for those cases.

Please let me know if that works well so I can merge it and close this issue. Thanks