From 8e5e5716f12de5f78258b851be3baf2caf3ab0de Mon Sep 17 00:00:00 2001 From: Lauri Ojansivu Date: Sat, 3 Jun 2017 17:49:12 +0300 Subject: [PATCH] jslint tips --- Developer-Documentation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Developer-Documentation.md b/Developer-Documentation.md index acaa57e..e638acd 100644 --- a/Developer-Documentation.md +++ b/Developer-Documentation.md @@ -42,7 +42,7 @@ Main point is to be friendly to those commenting of your code, and incorporate t - Templates are written in [JADE](https://naltatis.github.io/jade-syntax-docs/) instead of plain HTML. - CSS is written in the [Stylus](http://stylus-lang.com/) precompiler, and - Meteor templates are created as BlazeLayout templates. -- Eslint for linting. +- Eslint for linting. You can test for lint errors with "npm run lint" and if you want automatic fixes to that code file you can copy code to [jsbeautifer website](http://jsbeautifier.org) with settings Indent with 2 spaces (topmost dropdown), [X] Space before conditional: "if(x)" / "if (x)", [X] Use JSLint-happy formatting tweaks - Instead of the allow/deny paradigm a lot of the `collections` defined in the project use `mutations` to define what kinds of operations are allowed. For further details look for the 'feature summaries' in the Wiki (still in progress) otherwise go through the git history and see how old features were built. Might I suggest the Start and Due date feature [wefork#26](https://github.com/wefork/wekan/pull/26)