Microsoft/TypeScript

Inconsistent behavior of "export as" symbols.

开放

#30,223 创建于 2019年3月5日

 (6 条评论) (0 个反应) (0 位负责人)TypeScript (13,395 个派生)batch import
BugDomain: Error MessagesHelp Wanted

仓库指标

星标
 (108,860 个星标)
PR 合并指标
 (PR 指标待抓取)

描述

TypeScript Version: 3.4.0-dev.20190305

Search Terms: export alias

Code

This is file of some-lib:

export { LongNameOfInnerClass as PublicNameClass } from './long-name-of-inner-class';

This is other file, that import above lib:

import { PublicNameClass } from 'some-lib';

new PublicNameClass(); // Here hints is OK

new PublicNameClass(wrongArgument); // Error ref to LongNameOfInnerClass

Expected behavior: TypeScript hints have same "export as" aliases for working code and for errors.

Actual behavior: TypeScript hints for the working code are different from the hints for errors.

Related Issues: Not sure, but it seems that this issue has a similar problem: symbolToName does handle exports of namespaces

贡献者指南