We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Running rubocop on files in bin lacking permissions to be executed didn't give an offense that they can't be executed.
$ ls -la bin/ total 40 drwxr-xr-x 7 agrimm staff 238 20 Sep 15:43 . drwxr-xr-x 23 agrimm staff 782 21 Oct 14:37 .. -rw-r--r-- 1 agrimm staff 129 20 Sep 15:43 bundle -rw-r--r-- 1 agrimm staff 175 20 Sep 15:43 delayed_job -rw-r--r-- 1 agrimm staff 220 20 Sep 15:43 rails -rw-r--r-- 1 agrimm staff 164 20 Sep 15:43 rake -rw-r--r-- 1 agrimm staff 517 20 Sep 15:43 spring
Should RuboCop have the ability to detect this?
The main issues I can think of why it shouldn't are the following:
Reporting an offense for files which are in bin/ which are not executable.
New functionality.
Set a file in bin/ to have permissions -rw-r--r--.
-rw-r--r--
$ rubocop -V 0.44.1 (using Parser 2.3.1.4, running on ruby 2.1.10 x86_64-darwin14.0)
The text was updated successfully, but these errors were encountered:
This is definitely outside the scope of RuboCop.
Sorry, something went wrong.
No branches or pull requests
Running rubocop on files in bin lacking permissions to be executed didn't give an offense that they can't be executed.
Should RuboCop have the ability to detect this?
The main issues I can think of why it shouldn't are the following:
Expected behavior
Reporting an offense for files which are in bin/ which are not executable.
Actual behavior
New functionality.
Steps to reproduce the problem
Set a file in bin/ to have permissions
-rw-r--r--
.RuboCop version
The text was updated successfully, but these errors were encountered: