Referenced interfaces in TypeDoc might be wrong

Summary

Look here

This is more of a warning, there is little we can do outside of updating TypeDoc in the future because the issue probably won't be fixed in TypeDoc as it makes little sense from a documenting perspective to fix an issue with non-exported members. For now this is something that needs to be avoided inside the core to avoid issues with the mapping

Steps to reproduce

This is also important because it can be avoided easily

File a.ts

export interface Foo2 {}

interface Bar {
  a: number,
  b: string,
  c: unknown
}

File b.ts

export interface Foo1 {
  foo: Bar;
}

interface Bar {
  aa: number;
  cc: string;
}

In b.ts, foo will use the Bar from file a.ts. It overwrites based on the file name, so if the first file was named c.ts instead it wouldn't happen.

Example Project

You can look here if you want to reproduce the issue yourself.