You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
Andy (Andrewkraft) (@Andy-MS) This is again breaking our tests since typescript changed the enum values for SyntaxKind.
The issue here is that using dtslint essentially requires users to use typescript@next: tslint has a peerDependency on typescript so if one uses e.g. typescript@3.2 then tslint will parse the source with typescript@3.2. This results in nodes with different syntax kind enum values that are not recognized by typescript@next.
microsoft/TypeScript#25886 caused such an issue: tslint will create an AST where an export default ... node will have a modifier with the kind 84 which is the ExportKeyword in typescript@3.2 but since typescript 3.3 added the BigIntLiteralKeyword to SyntaxKind in typescript@nextExportKey will have the value 85. This reports a false positive in the strict-export-declare-modifer-rule.
Activity
eps1lon commentedon Feb 2, 2019
Andy (Andrewkraft) (@Andy-MS) This is again breaking our tests since typescript changed the enum values for
SyntaxKind.The issue here is that using
dtslintessentially requires users to usetypescript@next:tslinthas a peerDependency ontypescriptso if one uses e.g.typescript@3.2thentslintwill parse the source withtypescript@3.2. This results in nodes with different syntax kind enum values that are not recognized bytypescript@next.microsoft/TypeScript#25886 caused such an issue:
tslintwill create an AST where anexport default ...node will have a modifier with the kind84which is theExportKeywordintypescript@3.2but since typescript 3.3 added theBigIntLiteralKeywordtoSyntaxKindintypescript@nextExportKeywill have the value 85. This reports a false positive in thestrict-export-declare-modifer-rule.