-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dealing with Gemfile.lock #618
Comments
The |
so this is:
default config, no .standard.yml file |
okay, i added a simple .standard.yml file, but that does not seem to be honored. ruby_version: 3.3
ignore:
- Gemfile.lock
- tmp/**/*
- test/fixture/**/* |
sometimes there is a weird conflict about extensions when one has multiple sections in a workspace, but i've just opened the plain folder inside a simple vscodium instance (open vscode > open folder), and it's the same problem. |
hang on, just to be very clear: Gemfile.lock is not being ignored by default, right? Reference:
https://github.com/rubocop/rubocop/blob/v0.61.1/config/default.yml#L60-L63 If it is correct, why? What is the value in linting the Gemfile? And why does it create above mentioned error? |
To show a trivial example, given this folder with two files that are both non-compliant in the same way, only the
|
I get the same for Gemfile.lock, i.e. this in VSCode:
The first colon in I'm using the official StandardRB VSCode extension, and I have the following in
|
I think i am missing something about how to set up my linting/syntax checking, but for some reason in all my ruby projects, i get this error on the Gemfile.lock:
this is the part in question:
Context:
Should the file just be ignored, or what is exactly wrong here?
The text was updated successfully, but these errors were encountered: