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

Аутор	SHA1	Порука	Датум
Lyubo Marinov	c991abf9ef	[eslint] prefer-template	пре 8 година
Lyubo Marinov	5bff0ed543	[eslint] no-var	пре 8 година
hristoterezov	e4352d2188	fix(eslint): Add no-else-return rule	пре 8 година
Lyubo Marinov	4293971466	[eslint] operator-linebreak	пре 8 година
Lyubo Marinov	ed0d464392	[eslint] quotes	пре 8 година
Lyubo Marinov	f8ab8015a2	[eslint] space-before-blocks	пре 8 година
Lyubo Marinov	55ed404dd4	[eslint] space-in-parens	пре 8 година
Lyubo Marinov	14147059b3	[eslint] spaced-comment	пре 8 година
hristoterezov	c96898c478	fix(eslint): Add no-multi-spaces rule	пре 8 година
hristoterezov	f02a22d3f9	fix(eslint): Add brace-style rule	пре 8 година
hristoterezov	fceb8606d8	fix(eslint): Add no-extra-parens rule	пре 8 година
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.	пре 9 година
nikvaessen	77ef75f167	Sphinx now logs the error instead of throwing it	пре 9 година
nikvaessen	88235aaeed	added the Transcriber module	пре 9 година