Fix --plugin argument parsing (#682)

Currently, the `--plugin` argument simply doesn't work because it tries to treat the provided string as an array. For example, if I pass `--plugin foo`, it will try to load three npm packages named `f`, `o`, and `o` respectively.

This commit changes the option declaration to use the `ParameterType.Array` type, which parses a comma-separated string into an array. It also removes the otherwise-unused `isArray` property from the `DeclarationOptions` interface.

Author: tomdale

src/lib/utils/options/declaration.ts

@@ -26,7 +26,6 @@ export interface DeclarationOption {
     scope?: ParameterScope;
     map?: {};
     mapError?: string;
-    isArray?: boolean;
     defaultValue?: any;
     convert?: (param: OptionDeclaration, value?: any) => any;
 }

src/lib/utils/plugins.ts

@@ -11,8 +11,7 @@ export class PluginHost extends AbstractComponent<Application> {
     @Option({
         name: 'plugin',
         help: 'Specify the npm plugins that should be loaded. Omit to load all installed plugins, set to \'none\' to load no plugins.',
-        type: ParameterType.String,
-        isArray: true
+        type: ParameterType.Array
     })
     plugins: string[];
 

src/test/plugin-host.ts

@@ -0,0 +1,15 @@
+import { Application } from '..';
+import Assert = require('assert');
+
+describe('PluginHost', function () {
+  it('parses plugins correctly', function () {
+    let app = new Application({
+      plugin: 'typedoc-plugin-1,typedoc-plugin-2'
+    });
+
+    Assert.deepEqual(app.plugins.plugins, [
+      'typedoc-plugin-1',
+      'typedoc-plugin-2'
+    ]);
+  });
+});