Union type overload inference don't match if types are in different definitions

[kzarist]

Bug Report

🔎 Search Terms

overload inference union type

🕗 Version & Regression Information

4.5.4

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about it.

⏯ Playground Link

Playground link with relevant code

💻 Code

// library function definition

function libFunction(id: string | number): void;
function libFunction(conditions: {[key: string]: string}): void;
function libFunction(idOrConditions: string | number | {[key: string]: string}): void {
    console.log(idOrConditions);
}

// working example that matches a single definition
function myWrapper(id: string | number){
    libFunction(id);
}

myWrapper("something");
myWrapper(23)


// working example casting the param to any
// That's what I want to avoid
// Our code base is strict and using `any` obriglate
// me to use `eslint-disable` everywhere 
function myWrapperAny(idOrConditions: string | {[key: string]: string}){
    // eslint-disable-next-line
    libFunction(idOrConditions as any);
}

myWrapperAny("something");
myWrapperAny({name: "John"});

// non working wrapper
// Even if there are overloads from both types
// This just don't compile 
function myWrapper2(idOrConditions: string | {[key: string]: string}){
    libFunction(idOrConditions);
}

myWrapper2("something");
myWrapper2({name: "John"});

🙁 Actual behavior

No overload signature matches and code don't compile

🙂 Expected behavior

Overload signature matches and code compile

[whzx5byb]

Duplicate of #14107

[typescript-bot]

This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.