Suppress warnings for missing relative links

[jonchardy]

What's the best way to suppress warnings about relative paths missing for elements within comment blocks? These paths exist when our static site is built, but are not available relative to the source files as TypeDoc is resolving. None of the validation options allow me to suppress this type of warning.

Example:

/**
 * Method documentation.
 * 
 * This method may be overridden.
 * Please read <a href="../../intro/blah.html">this page</a> about how to override methods.
 */
public myMethod() {}

I get many warnings about such links:

./src/blah.ts:x:y - [warning] The relative path ../../intro/blah.html is not a file and will not be copied to the output directory

123       * Please read <a href="../../intro/blah.html">this page</a> about how to override methods.

Thanks.

[Gerrit0]

There's no way to suppress this option yet, adding one won't be too much work.... but how should it work?

My first thought here was to have an option which listed paths relative to the config file which should be accepted as relative links and just ignored, but given that you say you have many such warnings, it seems like you'd prefer some sort of option which accepts a directory or something where relative links within it would be ignored.... thoughts?

[jonchardy]

I just imagined it as another boolean option on validation which would suppress all such errrors if it was set to false.

For our use case, we'd just need to ignore a couple of folders that end up as siblings of the documentation on our site. For example, we have abc.com/intro/foo.html or abc.com/samples/bar.html, which are linked to from abc.com/api/MyClass.html but are structured differently relative to the source files that the docs are generated from.