Repository navigation
Update declaration of ts.Iterator to be compatible with ES2015 IteratorResult type #32890
Description
This is the same issue as #31214 as that one was closed even though the error still exists in the most recent nightly build.
TypeScript Version: 3.6.0-dev.20190814
Search Terms:
Code
I'm trying to use the API changes of #31101, but I run into assignability issues.
// @strict: true
// @target: es2015
import * as ts from 'typescript';
return ts.getParsedCommandLineOfConfigFile('foo', {}, undefined!, new Map<string, ts.ExtendedConfigCacheEntry>());Expected behavior:
No type error.
Actual behavior:
Argument of type 'Map<string, ExtendedConfigCacheEntry>' is not assignable to parameter of type 'Map<ExtendedConfigCacheEntry>'.
Types of property 'keys' are incompatible.
Type '() => IterableIterator<string>' is not assignable to type '() => Iterator<string>'.
Type 'IterableIterator<string>' is not assignable to type 'Iterator<string>'.
Types of property 'next' are incompatible.
Type '(value?: any) => IteratorResult<string>' is not assignable to type '() => { value: never; done: true; } | { value: string; done: false; }'.
Type 'IteratorResult<string>' is not assignable to type '{ value: never; done: true; } | { value: string; done: false; }'.
Type 'IteratorResult<string>' is not assignable to type '{ value: string; done: false; }'.
Types of property 'done' are incompatible.
Type 'boolean' is not assignable to type 'false'.
Activity
PhoenixHe-NV commentedon Aug 29, 2019
I have the same issue here. After upgrading to typescript 3.6.2 my project failed to compile because of
IterableIterator<string>andIterator<string>are not compatible.