{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/kibana/issues/4949","labels_url":"https://api.github.com/repos/elastic/kibana/issues/4949/labels{/name}","comments_url":"https://api.github.com/repos/elastic/kibana/issues/4949/comments","events_url":"https://api.github.com/repos/elastic/kibana/issues/4949/events","html_url":"https://github.com/elastic/kibana/issues/4949","id":106642510,"number":4949,"title":"ES6 style guide updates","user":{"login":"w33ble","id":404731,"avatar_url":"https://avatars.githubusercontent.com/u/404731?v=3","gravatar_id":"","url":"https://api.github.com/users/w33ble","html_url":"https://github.com/w33ble","followers_url":"https://api.github.com/users/w33ble/followers","following_url":"https://api.github.com/users/w33ble/following{/other_user}","gists_url":"https://api.github.com/users/w33ble/gists{/gist_id}","starred_url":"https://api.github.com/users/w33ble/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/w33ble/subscriptions","organizations_url":"https://api.github.com/users/w33ble/orgs","repos_url":"https://api.github.com/users/w33ble/repos","events_url":"https://api.github.com/users/w33ble/events{/privacy}","received_events_url":"https://api.github.com/users/w33ble/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/elastic/kibana/labels/dev","name":"dev","color":"006b75"},{"url":"https://api.github.com/repos/elastic/kibana/labels/discuss","name":"discuss","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-09-15T20:44:16Z","updated_at":"2015-09-15T21:19:36Z","closed_at":null,"body":"Now that we're running all of our code through Babel, and we're starting to use ES6, we need to make some decisions about how and when to use it, and update the style guide accordingly.\r\n\r\nThings to consider:\r\n\r\n- When we can use fat arrow\r\n- `let` and `const`\r\n- `context` in tests (as an alias for `describe`)\r\n- When and how to unwrap AMD modules\r\n- snake_case vs camelCase file names"},"comment":{"url":"https://api.github.com/repos/elastic/kibana/issues/comments/140548015","html_url":"https://github.com/elastic/kibana/issues/4949#issuecomment-140548015","issue_url":"https://api.github.com/repos/elastic/kibana/issues/4949","id":140548015,"user":{"login":"tsullivan","id":908371,"avatar_url":"https://avatars.githubusercontent.com/u/908371?v=3","gravatar_id":"","url":"https://api.github.com/users/tsullivan","html_url":"https://github.com/tsullivan","followers_url":"https://api.github.com/users/tsullivan/followers","following_url":"https://api.github.com/users/tsullivan/following{/other_user}","gists_url":"https://api.github.com/users/tsullivan/gists{/gist_id}","starred_url":"https://api.github.com/users/tsullivan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tsullivan/subscriptions","organizations_url":"https://api.github.com/users/tsullivan/orgs","repos_url":"https://api.github.com/users/tsullivan/repos","events_url":"https://api.github.com/users/tsullivan/events{/privacy}","received_events_url":"https://api.github.com/users/tsullivan/received_events","type":"User","site_admin":false},"created_at":"2015-09-15T21:19:36Z","updated_at":"2015-09-15T21:19:36Z","body":"I agree with using `describe` and `context` to keep the structure of tests hierarchically organized and semantics. But it does mean that as reviewers, when we look at test code, we need to be clear that describe is the outer function to use, and context is the inner one. The code won't complain if we switch them.\r\n\r\nI'm not sure if there is a lint rule for keeping the order correct- that would be ideal."}}