Updating readme with better configuration option documentation

README.md

@@ -48,6 +48,34 @@ The plugin has so far *only been tested on Windows* and it'll be no surprise if
 * Run sonar-runner
 * TsLint rule breaches should be shown in the web view
 
+##Configuration
+
+###Global configuration
+
+<table>
+<thead>
+<tr><th>Key</th><th></th><th>Description</th></thead>
+<tbody>
+<tr><td>sonar.ts.tslintpath</td><td><b>Mandatory</b></td><td>Path to the installed copy of TsLint to use</td></tr>
+</tbody>
+</table>
+
+###Project-level configuration
+
+<table>
+<thead>
+<tr><th>Key</th><th></th><th>Description</th>
+</thead>
+<tbody>
+<tr><td>sonar.ts.tslintconfigpath</td><td><b>Mandatory</b></td><td>Path to the tslint.json file that configures the rules to be used in linting</td></tr>
+<tr><td>sonar.ts.excludetypedefinitionfiles</td><td><b>Optional</b></td><td>Excludes .d.ts files from analysis</td></tr>
+<tr><td>sonar.ts.forceZeroCoverage</td><td><b>Optional</b></td><td>Forces code coverage percentage to zero when no report is supplied</td></tr>
+<tr><td>sonar.ts.tslinttimeout</td><td><b>Optional</b></td><td>Max time to wait for TsLint to finish processing a single file (in milliseconds), defaults to 60 seconds</td></tr>
+<tr><td>sonar.ts.tslintrulesdir</td><td><b>Optional</b></td><td>Path to a folder containing custom TsLint rules referenced in tslint.json</td></tr>
+<tr><td>sonar.ts.lcov.reportpath</td><td><b>Optional</b></td><td>Path to an LCOV code-coverage report to be included in analysis</td></tr>
+</tbody>
+</table>
+
 ##Licence
 MIT