Repository navigation
Implementing an interface suggests any as type聽#47281
Description
Bug Report
When you auto implement an interface, I would not expect TypeScript to suggest the any type.
馃攷 Search Terms
auto complete
馃捇 Code
interface OperatingSystem {
}
interface IPathService {
hasValidBasename(resource: string, basename?: string): Promise<boolean>;
hasValidBasename(resource: string, os: OperatingSystem, basename?: string): boolean;
}
class PathService implements IPathService {
// Let TS implement the interface!
}馃檨 Actual behavior
hasValidBasename(resource: string,basename?: string): Promise<boolean>;
hasValidBasename(resource: string,os: OperatingSystem,basename?: string): boolean;
hasValidBasename(resource: any,os?: any,basename?: any): boolean|Promise<boolean> {
throw new Error("Method not implemented.");
}馃檪 Expected behavior
hasValidBasename(resource: string,basename?: string): Promise<boolean>;
hasValidBasename(resource: string,os: OperatingSystem,basename?: string): boolean;
hasValidBasename(resource: string,os?: arg2: basename | OperatingSystem,basename?: string): boolean|Promise<boolean> {
throw new Error("Method not implemented.");
}At the very minimum, put unknown.
Activity
RyanCavanaugh commentedon Jan 3, 2022
unknowndoes seem better here