Zack Elliott

I wonder if this will be addressed by https://github.com/microsoft/tsdoc/pull/325. @rbuckton?

Thanks for the thorough comments! Some responses below: Re your first comment: For the record, I definitely see the value of `ae-forgotten-export` and am not proposing to remove the warning...

> Won't `UserInputBase` be visible in the .d.ts file? In VS Code, if I right click on `button.disabled` and do "Go to definition", it's going to take me to the...

> In the projects that I've worked on, I think what would happen is that people would still forget, and in some cases it would still create problems. (*"Why didn't...

> When that feature is turned on, what do the URLs look like? I was thinking the following for Option 1: * **`UserInputBase` not exported:** * URL for `Button.disabled` (inherited)...

> Fluent UI has very brief documentation for each property, so they just put everything on one page, which sidesteps the problem of duplicated URLs: Our primary use case right...

Quick note: Another real-world example of unexported base classes is the mixin pattern used extensively within api-extractor-model.

After a long discussion between @octogonz and myself today, we concluded that API Extractor should no longer treat base classes that are only "reachable" via inheritance as "forgotten exports". That...

From my brief investigation, it looks like API Extractor is potentially processing your project's `.ts` files. It should process `.d.ts` files, not `.ts` files. But if that was the case,...

Thanks! I added `showDiagnostics: true` to your `Extractor.invoke(...)` call and confirmed that API Extractor appears to be running on both `.d.ts` and `.ts` files. It should only run on `.d.ts`...