microsoft / microsoft/TypeScript
Unable to return ElementFinder from an async function in TS 3.9
@rbuckton arbeitet bereits daran.
Seit 19.10.2020.
- Vorherrschende Sprache
- Go
- Sterne
- 111k
- Forks
- 14.3k
- Ø Merge
- 1 T. 19 Std.
- Gemergte PRs (30 T.)
- 117
Beschreibung
TypeScript Version: 3.9.2
Search Terms:
The return type of an async function must either be a valid promise or must not contain a callable 'then' member.(1058)
Code
export declare class ElementFinder {
then?: (fn: (value: any) => any, errorFn?: (error: any) => any) => Promise<any>;
}
export declare class ElementArray{
first(): ElementFinder;
}
export async function assertSingleElement( // error: The return type of an async function must either be a valid promise or must not contain a callable 'then' member.(1058)
array: ElementArray,
): Promise<ElementFinder> {
//await something up here so require async function
return array.first() as any;
}
This code works in 3.8.
Expected behavior:
We should be able to compile the above code or at least tell TS to ignore the error and compile anyway.
Actual behavior:
There is no way that I could find to return an object with a then function from an async function.
This is ultimately an issue with Protractor. The "workaround" is to edit the d.ts files in node_modules which for most build chains is not an option at all. Related issue:
https://github.com/angular/protractor/issues/3831
In the above function I am trying to return an ElementFinder object from an async function. ElementFinder is a badly typed Promise type thing but I don't want the ElementFinder to be resolved, I want an unresolved ElementFinder to be returned and to be used in the calling function. It seems that the then function is breaking TS and there doesn't seem to be any way to trick TS into allowing this.
This worked fine in 3.8 but breaks in 3.9 and currently preventing us from upgrading to Angular 10.
How to I trick TS into allowing this?
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.