{"action":"created","issue":{"url":"https://api.github.com/repos/eslint/eslint/issues/3483","labels_url":"https://api.github.com/repos/eslint/eslint/issues/3483/labels{/name}","comments_url":"https://api.github.com/repos/eslint/eslint/issues/3483/comments","events_url":"https://api.github.com/repos/eslint/eslint/issues/3483/events","html_url":"https://github.com/eslint/eslint/issues/3483","id":102496564,"number":3483,"title":"Extensive mode and thorough analysis","user":{"login":"denis-sokolov","id":113721,"avatar_url":"https://avatars.githubusercontent.com/u/113721?v=3","gravatar_id":"","url":"https://api.github.com/users/denis-sokolov","html_url":"https://github.com/denis-sokolov","followers_url":"https://api.github.com/users/denis-sokolov/followers","following_url":"https://api.github.com/users/denis-sokolov/following{/other_user}","gists_url":"https://api.github.com/users/denis-sokolov/gists{/gist_id}","starred_url":"https://api.github.com/users/denis-sokolov/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/denis-sokolov/subscriptions","organizations_url":"https://api.github.com/users/denis-sokolov/orgs","repos_url":"https://api.github.com/users/denis-sokolov/repos","events_url":"https://api.github.com/users/denis-sokolov/events{/privacy}","received_events_url":"https://api.github.com/users/denis-sokolov/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/eslint/eslint/labels/triage","name":"triage","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-08-22T02:21:33Z","updated_at":"2015-08-23T01:22:07Z","closed_at":null,"body":"There are a lot of interesting static analysis checks eslint can do to detect potential errors,\r\nthat are impossible to implement in a fast manner to fit the current performance budget of the tool.\r\n(Running it interactively in the editor)\r\n\r\nWhat if we had a convenient method, a common workflow to run extensive checks on a CI server, with a considerably bigger performance budget? After all, in the world of C, you'd use your compiler, or valgrind, or [clang analyzer](http://clang-analyzer.llvm.org/) without a hope to run it interactively in milliseconds, and yet gaining big value from detected bug, even if not in real-time.\r\n\r\nOf course, we can use a different tool or manually set up a separate run of eslint with a different toolset, but support from the core is important for adoption and development of such a mode.\r\nBy blessing a workflow like this, by categorizing the rules into \"slow\" and \"fast\" and by allowing \"slow\" rules to exist, eslint might bring another level up for error-detecting in js programs.\r\n\r\nAny chance of a feature like this being added?\r\n"},"comment":{"url":"https://api.github.com/repos/eslint/eslint/issues/comments/133768964","html_url":"https://github.com/eslint/eslint/issues/3483#issuecomment-133768964","issue_url":"https://api.github.com/repos/eslint/eslint/issues/3483","id":133768964,"user":{"login":"ilyavolodin","id":1380062,"avatar_url":"https://avatars.githubusercontent.com/u/1380062?v=3","gravatar_id":"","url":"https://api.github.com/users/ilyavolodin","html_url":"https://github.com/ilyavolodin","followers_url":"https://api.github.com/users/ilyavolodin/followers","following_url":"https://api.github.com/users/ilyavolodin/following{/other_user}","gists_url":"https://api.github.com/users/ilyavolodin/gists{/gist_id}","starred_url":"https://api.github.com/users/ilyavolodin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ilyavolodin/subscriptions","organizations_url":"https://api.github.com/users/ilyavolodin/orgs","repos_url":"https://api.github.com/users/ilyavolodin/repos","events_url":"https://api.github.com/users/ilyavolodin/events{/privacy}","received_events_url":"https://api.github.com/users/ilyavolodin/received_events","type":"User","site_admin":false},"created_at":"2015-08-23T01:22:07Z","updated_at":"2015-08-23T01:22:07Z","body":"I see why you'd need that, however, I think that while slower rules might bring enough value, they will be that, slower. It feels like those rules should be separated into a plugin and then people who would want to run them on CI, could just add that plugin. I'm not really sure about adding rules like that to the core."}}