-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Allow export default interface #3914
Comments
You can get around this with interface I {
}
export default I; I admit this is a somewhat strange inconsistency, but this is a duplicate of #3194 and is by design in accordance with a decision made on #3095 (comment). |
Interesting. Any chance there could be a warning about the behavior? |
Linking to #3792 because they're very similar. We should just allow this kind of thing. There's no good reason to require you to write it in 2 statements instead of one. |
👍 Currently I am doing the "workaround" with everything for consistency, would be nice to switch though. |
👍 Any kind of error would be welcome, it took a StackOverflow question to understand. |
closing in favor of #3792 |
The following snippet is valid, as far as I know:
The following snippet is also valid, but does not compile, but probably should:
I get errors thrown at me when using TypeScript 1.5-beta:
The text was updated successfully, but these errors were encountered: