Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
No longer formatting files
See original GitHub issueIn Rubocop 0.87.0 the behaviour of autocorrect (-a) was changed (https://github.com/rubocop-hq/rubocop/issues/8156).
I assume this extension is using -a since it has stopped formatting my .rb files with the frozen_string_literal comment.
To get the same formatting behaviour as before the flag needs to now be -A (more info).
I assume this issue is the same as https://github.com/misogi/vscode-ruby-rubocop/issues/120, https://github.com/misogi/vscode-ruby-rubocop/issues/121.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have the same problem. Extension reports an error during autocorrection, but I found no log to trace back and debug.
Annoyingly RuboCop 0.86 suffers from https://github.com/rubocop-hq/rubocop/issues/8713 :