`validation.notDocumented` doesn't correctly handle some cases

Search terms

function type definitions, methods with computed names, generated types

Expected Behavior

Enabling validation.notDocumented should correctly report on:

• function type definitions (type Foo = () => void)
• methods with computed names:

  const name = "foo";
  class SomeClass {
    [name]() { return "huh"; }
  }
  

• methods inside generated definitions used by excluded methods:

  class SomeClass {
    doSomething() {
      return {
        foo() {}
      }
    }
  }
  

Actual Behavior

All of the above cases falsely report that they are undocumented.

Steps to reproduce the bug

1. Clone the main branch of https://github.com/thislooksfun/typedoc-repros
2. Install deps and run npm run gendoc
3. The docs should be generated without any warning. Instead, it prints:

Warning: FunctionType, defined at index.ts:2, does not have any documentation.
Warning: [iterator], defined at index.ts:7, does not have any documentation.
Warning: index, defined at index.ts:10, does not have any documentation.
Warning: next, defined at index.ts:12, does not have any documentation.
Warning: next, defined at index.ts:28, does not have any documentation.

Environment

• Typedoc version: HEAD (98841f5b6c79a2314f5bde6d328fe0b6f4e56bea)
• TypeScript version: any
• Node.js version: 16
• OS: macOS

[Gerrit0]

Well, there’s that fixed… hopefully this lasts longer than the other one before horrible bugs are discovered 😉

[thislooksfun]

I can confirm that my project now passes without error when run against ea16a7b4885abd9ee3ee7ef28ded0e4293f1ee7c! I’m probably not using every possible reflected type, but I ran with requiredToBeDocumented set to everything other than "Project" and got 0 false matches.