-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
improve rubocop-todo #702
Comments
I think both are good ideas. I'll try to implement them. |
I think the comments are prone to be out of sync with actual project status and latest RuboCop autocorrect support. |
@yujinakayama true, but every new release of rubocop requires me to run |
Then, I think it would be better if the following are also in the comments:
|
sounds good to me. |
I've made changes to produce the comments we've discussed, and also comments about configuration parameters, which I think could be helpful. Sometimes a parameter can be changed and there's no need to disable the cop entirely. I want to make that clear to the user. Something like this: # This configuration was generated by `rubocop --auto-gen-config`
# on 2013-12-31 15:20:00 +0100 using RuboCop version 0.16.0.
# The point is for the user to remove these configuration records
# one by one as the offences are removed from the code base.
# Note that changes in the inspected code, or installation of new
# versions of RuboCop, may require this file to be generated again.
# Offence count: 1.
# Configuration parameters: EnforcedStyle, SupportedStyles.
AccessModifierIndentation:
Enabled: false
# Offence count: 6.
CyclomaticComplexity:
Max: 15
# Offence count: 11.
Documentation:
Enabled: false
# Offence count: 29.
# Configuration parameters: AllowedVariables.
GlobalVars:
Enabled: false
# Offence count: 20.
# Configuration parameters: CountComments.
MethodLength:
Max: 30
# Offence count: 1.
# Cop supports --auto-correct.
TrailingWhitespace:
Enabled: false @tamird @yujinakayama What do yo think? |
Oh that's awesome. Could we make it print acceptable values for the configuration parameters, too? Maybe not necessary if it's an integer, but great for |
Um, I think we have to draw the line somewhere. 😄 The parameters and their descriptions are available in |
Okay, sounds good. I had dealt with |
@jonas054 I don't think that a line like |
Ah, I just sent a pull request exactly the same time as your comment. I'll remove the |
[Fix #702] Add comments for cops in rubocop-todo.yml.
Couple of simple ideas for rubocop-todo.
--format offences
gives).cc @jonas054
The text was updated successfully, but these errors were encountered: