-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removing the qualified name restriction on import targets #1166
Comments
Another use-case described in #3832 |
Approved. There is some slight subtlety here -- consider the following code: namespace X {
interface window { }
export import Y = window;
}
// What is the meaning of X.Y? You can think of two different resolution algorithms that we could use on line 3:
The second interpretation is more predictable and is more likely to be what's intended. |
This is labeled as easy, for someone who is a novice to TypeScript could some guidance on implementation be added to the issue so we could look into contributing a PR? |
I agree with @jbcpollak. Even I feel that there should be some amount of guidance. |
I would start looking at |
Is this still a problem? as I was able to do this:
B.ts
on 3.6.3 |
Hi, |
It seems to me, it's very inconvenient, that import declaration can't have none qualified symbol as target. By the reason I have to use next way to do this:
Maybe, removing the qualified name restriction will be more convenient than combination of type alias and var alias.
The text was updated successfully, but these errors were encountered: