jfinn/ljm_j1 - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Lyubo Marinov	068f290835	[eslint] lines-around-comment	8 years ago
Lyubo Marinov	4581605a28	[eslint] newline-after-var, newline-before-return, newline-per-chained-call	8 years ago
Lyubo Marinov	1068233eac	[eslint] prefer-rest-params	8 years ago
Lyubo Marinov	5bff0ed543	[eslint] no-var	8 years ago
Lyubo Marinov	4293971466	[eslint] operator-linebreak	8 years ago
Lyubo Marinov	ed0d464392	[eslint] quotes	8 years ago
Lyubo Marinov	78217478d1	[eslint] space-before-function-paren	8 years ago
Lyubo Marinov	14147059b3	[eslint] spaced-comment	8 years ago
hristoterezov	c96898c478	fix(eslint): Add no-multi-spaces rule	8 years ago
hristoterezov	3e44723582	fix(eslint): Add indent rule	8 years ago
hristoterezov	f02a22d3f9	fix(eslint): Add brace-style rule	8 years ago
hristoterezov	c36b464bfc	fix(eslint): Add curly rule	8 years ago
hristoterezov	fceb8606d8	fix(eslint): Add no-extra-parens rule	8 years ago
Lyubomir Marinov	90ee7e8a54	ESLint Our JSHint configuration is not extensive and we have excluded multiple files from linting. Additionally, we have seen JSHint to be unable to parse newer ECMAScript features such as the object spread operator (proposal). On the other hand, we have seen ESLint to beautifully work on React and React Native source code in addition to ES2015 and later. Introduce ESLint alongside JSHint as an intermediate step to eventually switching from JSHint to ESLint. As our source code does not fully follow even the JSHint rules we have, it is very difficult to introduce ESLint with many rules. At the beginning, introduce it with as little rules as possible. Morever, ESLint is able to automatically fix certain rule offenders so once we have ESLint merged we can incrementally add new rules while keeping our commits' modification on as little subjects as possible.	8 years ago
hristoterezov	342e8ac5c0	Simplifies EventEmitterForwarder.forward code	8 years ago
hristoterezov	faeda96206	Implements reload method in JitsiConference	8 years ago