{"action":"created","issue":{"url":"https://api.github.com/repos/eslint/eslint/issues/3380","labels_url":"https://api.github.com/repos/eslint/eslint/issues/3380/labels{/name}","comments_url":"https://api.github.com/repos/eslint/eslint/issues/3380/comments","events_url":"https://api.github.com/repos/eslint/eslint/issues/3380/events","html_url":"https://github.com/eslint/eslint/issues/3380","id":100577730,"number":3380,"title":"`space-infix-ops` should either cover AssignmentPattern too or not cover VariableDeclaration","user":{"login":"BYK","id":126780,"avatar_url":"https://avatars.githubusercontent.com/u/126780?v=3","gravatar_id":"","url":"https://api.github.com/users/BYK","html_url":"https://github.com/BYK","followers_url":"https://api.github.com/users/BYK/followers","following_url":"https://api.github.com/users/BYK/following{/other_user}","gists_url":"https://api.github.com/users/BYK/gists{/gist_id}","starred_url":"https://api.github.com/users/BYK/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BYK/subscriptions","organizations_url":"https://api.github.com/users/BYK/orgs","repos_url":"https://api.github.com/users/BYK/repos","events_url":"https://api.github.com/users/BYK/events{/privacy}","received_events_url":"https://api.github.com/users/BYK/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":1,"created_at":"2015-08-12T16:01:23Z","updated_at":"2015-08-12T16:01:24Z","closed_at":null,"body":"#3299 sparked a new discussion:\r\n\r\nNormally, the name `space-infix-ops` is not expected to cover `=` because it is not an operator but an \"init statement\". (paraphrased @michaelficarra) but #465 made it cover `VariableDefinition`, thus `=`. With the introduction of ES6 features, it has now lagged behind and does not cover \"function defaults\" and `=` sign in object destructuring.\r\n\r\nExpectation is this rule to either cover all cases where `=` is used or not cover it at all (thus be consistent)."},"comment":{"url":"https://api.github.com/repos/eslint/eslint/issues/comments/130355629","html_url":"https://github.com/eslint/eslint/issues/3380#issuecomment-130355629","issue_url":"https://api.github.com/repos/eslint/eslint/issues/3380","id":130355629,"user":{"login":"eslintbot","id":13383618,"avatar_url":"https://avatars.githubusercontent.com/u/13383618?v=3","gravatar_id":"","url":"https://api.github.com/users/eslintbot","html_url":"https://github.com/eslintbot","followers_url":"https://api.github.com/users/eslintbot/followers","following_url":"https://api.github.com/users/eslintbot/following{/other_user}","gists_url":"https://api.github.com/users/eslintbot/gists{/gist_id}","starred_url":"https://api.github.com/users/eslintbot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eslintbot/subscriptions","organizations_url":"https://api.github.com/users/eslintbot/orgs","repos_url":"https://api.github.com/users/eslintbot/repos","events_url":"https://api.github.com/users/eslintbot/events{/privacy}","received_events_url":"https://api.github.com/users/eslintbot/received_events","type":"User","site_admin":false},"created_at":"2015-08-12T16:01:24Z","updated_at":"2015-08-12T16:01:24Z","body":"Thanks for the issue! We get a lot of issues, so this message is automatically posted to each one to help you check that you've included all of the information we need to help you.\n\nReporting a bug? Please be sure to include:\n\n1. The version of ESLint you are using (run `eslint -v`)\n1. The source code that caused the problem\n1. The configuration you're using (for the rule or your entire config file)\n1. The actual ESLint output complete with line numbers\n\nRequesting a new rule? Please be sure to include:\n\n1. The use case for the rule - what is it trying to prevent or flag?\n1. Whether the rule is trying to prevent an error or is purely stylistic\n1. Why you believe this rule is generic enough to be included\n\nRequesting a feature? Please be sure to include:\n\n1. The problem you want to solve (don't mention the solution)\n1. Your take on the correct solution to problem\n\nIncluding this information in your issue helps us to triage it and get you a response as quickly as possible.\n\nThanks!"}}