{"push_id":1325985473,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"9c9c3087ad3124e830fa89a5ab4e2664a7dfa5bc","before":"997122de20ec0b0529133e010f3416c97d7e8f75","commits":[{"sha":"90ee7e8a54089ae6b60d0202dcd93d3195acd72c","author":{"name":"Lyubomir Marinov","email":"af078e0d30d8b2e5793add4645afd5456e00834d@jitsi.org"},"message":"ESLint\n\nOur JSHint configuration is not extensive and we have excluded multiple\nfiles from linting. Additionally, we have seen JSHint to be unable to\nparse newer ECMAScript features such as the object spread operator\n(proposal).\n\nOn the other hand, we have seen ESLint to beautifully work on React and\nReact Native source code in addition to ES2015 and later. Introduce\nESLint alongside JSHint as an intermediate step to eventually switching\nfrom JSHint to ESLint.\n\nAs our source code does not fully follow even the JSHint rules we have,\nit is very difficult to introduce ESLint with many rules. At the\nbeginning, introduce it with as little rules as possible. Morever,\nESLint is able to automatically fix certain rule offenders so once we\nhave ESLint merged we can incrementally add new rules while keeping our\ncommits' modification on as little subjects as possible.","distinct":false,"url":"https://api.github.com/repos/jitsi/lib-jitsi-meet/commits/90ee7e8a54089ae6b60d0202dcd93d3195acd72c"},{"sha":"9c9c3087ad3124e830fa89a5ab4e2664a7dfa5bc","author":{"name":"hristoterezov","email":"4669287f2a404b0c05c00a721f4a375b0d716b9f@jitsi.org"},"message":"Merge pull request #260 from jitsi/eslint\n\nESLint","distinct":true,"url":"https://api.github.com/repos/jitsi/lib-jitsi-meet/commits/9c9c3087ad3124e830fa89a5ab4e2664a7dfa5bc"}]}
{"actor":{"display_login":"hristoterezov"}}