{"action":"opened","issue":{"url":"https://api.github.com/repos/bbatsov/rubocop/issues/2424","labels_url":"https://api.github.com/repos/bbatsov/rubocop/issues/2424/labels{/name}","comments_url":"https://api.github.com/repos/bbatsov/rubocop/issues/2424/comments","events_url":"https://api.github.com/repos/bbatsov/rubocop/issues/2424/events","html_url":"https://github.com/bbatsov/rubocop/issues/2424","id":116454045,"number":2424,"title":"rubocop_todo specific behavior","user":{"login":"deivid-rodriguez","id":2887858,"avatar_url":"https://avatars.githubusercontent.com/u/2887858?v=3","gravatar_id":"","url":"https://api.github.com/users/deivid-rodriguez","html_url":"https://github.com/deivid-rodriguez","followers_url":"https://api.github.com/users/deivid-rodriguez/followers","following_url":"https://api.github.com/users/deivid-rodriguez/following{/other_user}","gists_url":"https://api.github.com/users/deivid-rodriguez/gists{/gist_id}","starred_url":"https://api.github.com/users/deivid-rodriguez/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/deivid-rodriguez/subscriptions","organizations_url":"https://api.github.com/users/deivid-rodriguez/orgs","repos_url":"https://api.github.com/users/deivid-rodriguez/repos","events_url":"https://api.github.com/users/deivid-rodriguez/events{/privacy}","received_events_url":"https://api.github.com/users/deivid-rodriguez/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-12T00:41:15Z","updated_at":"2015-11-12T00:41:15Z","closed_at":null,"body":"#### Request\r\n\r\nRight now `rubocop_todo.yml` behaves just like `.rubocop.yml`, but it has some helpful comments and it's supposed to be removed. I always expected their behavior to be a little different.\r\n\r\nI'd like `.rubocop_todo.yml` to have an extra `Limit` parameter for each Cop, say\r\n\r\n```yaml\r\nMetrics/MethodLength:\r\n  Max: 80\r\n  Limit: 13\r\n```\r\n\r\nand I'd like RuboCop to fail if I exceed that number of offenses.\r\n\r\nI would then have several options:\r\n\r\n- Fix the issue(s) I've introduced. (Do it now)\r\n- Rebuild my todo config to have `Limit: 14` (or whatever), so RuboCop wouldn't shout again unless I have more than the new number of offenses. (Do it later)\r\n- Move the `Max: 80` configuration to the regular `.rubocop.yml` (Don't do it)\r\n\r\nI would also like the `rubocop_todo.yml` to be updated when the `Limit` parameter is reduced.\r\n\r\n#### Rationale\r\n\r\nThe configurations in `.rubocop_todo.yml` file are supposed to be removed, so I think we could help the user with that. In the previous case, the user could keep writing huge methods but Rubocop won't give any feedback, so removing the offenses will get harder and harder. If we raised a flag when limits are exceeded the user would be more aware about the kind of code (s)he is writing and whether (s)he wants to fix it.\r\n\r\nMaybe some users won't be interested, so RuboCop could behave like this under a `--strict` flag or something.\r\n\r\nI have no idea how difficult this would be to implement, but I thought I would throw this out and see what you guys think."}}