Avoid documenting excluded files.

[Gerrit0]

This is an attempt at correcting how the exclude option works. I'd like to get some feedback from people running into this problem before merging these changes in.

I previously raised some concerns about how a change like this would affect errors/output, so here's how I decided to handle each concern:

1. If TypeScript reports that a diagnostic message is not linked to a source file, it is still logged as an error.
2. If TypeScript reports that a diagnostic message is linked to a source file returned by Application.expandInputFiles it is still logged as an error.
3. Otherwise, the error will be suppressed since it belongs to a file which was not originally included by the user.

I ran the project on the TypeDoc repo with the utils folder excluded and noted that classes defined in the utils folder were not present in the JSON output. In the HTML output, their name will be printed as plain text (much like Promise) if they are referred. I also introduced errors both in the utils folder and outside of the utils folder and noted that only errors outside of the utils folder were reported. Errors in the utils folder did not prevent output.

Fixes #319
Fixes #839

[slinkardbrandon]

When I npm link this branch in typedoc to my project I'm running into an issue with the ConvertComponent invocation.

typedoc

Error: The plugin /Users/bslinkard/someproject/node_modules/typedoc-plugin-markdown could not be loaded.

TypeError: Class constructor ConverterComponent cannot be invoked without 'new'
    at new MarkdownPlugin (/Users/bslinkard/someproject/node_modules/typedoc-plugin-markdown/dist/plugin.js:31:42)
    at Converter.addComponent (/Users/bslinkard/www/typedoc/dist/lib/utils/component.js:123:19)
    at Converter.addComponent (/Users/bslinkard/www/typedoc/dist/lib/converter/converter.js:28:33)
    at module.exports (/Users/bslinkard/someproject/node_modules/typedoc-plugin-markdown/dist/index.js:36:19)
    at PluginHost.load (/Users/bslinkard/www/typedoc/dist/lib/utils/plugins.js:36:21)
    at CliApplication.bootstrap (/Users/bslinkard/www/typedoc/dist/lib/application.js:42:22)
    at CliApplication.bootstrap (/Users/bslinkard/www/typedoc/dist/lib/cli.js:24:30)
    at new Application (/Users/bslinkard/www/typedoc/dist/lib/application.js:31:14)
    at new CliApplication (/Users/bslinkard/www/typedoc/dist/lib/cli.js:22:1)
    at Object.<anonymous> (/Users/bslinkard/www/typedoc/bin/typedoc:4:1)

Using TypeScript 3.1.1 from /Users/bslinkard/www/typedoc/node_modules/typescript/lib
Rendering [========================================] 100%
Error: Documentation could not be generated due to the errors above.

In my package.json:

    "docs": "typedoc --exclude node_modules"

In my tsconfig.json:

"typedocOptions": {
    "mode": "file",
    "out": "docs",
    "theme": "minimal",
    "exclude": ["test", "node_modules"],
    "excludePrivate": true,
    "excludeNotExported": true,
    "moduleResolution": "node",
    "module": "commonjs",
    "hideGenerator": true,
    "readme": "none"
  }

[Gerrit0]

That's... odd to say the least. I don't think it's related to this PR since the source of the error appears to be the markdown plugin you have installed.

at new MarkdownPlugin (/Users/bslinkard/someproject/node_modules/typedoc-plugin-markdown/dist/plugin.js:31:42)

I'd be willing to bet that npm link won't work with plugins since there are multiple node_modules folders, but I haven't tested to confirm this

[balupton]

When will this land?

[9oelM]

Got merged!

[balupton]

Great! When will a release land?

[aciccarello]

I'm planning on merging #922 before pushing a release