Skip to content
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

TS4029: Public property 'baz' of exported class has or is using name 'Baz' from external module "C:/Main/Work/ts-export-bug/A" but cannot be named. #19712

Closed
PFight opened this issue Nov 3, 2017 · 5 comments
Labels
Duplicate An existing issue was already created

Comments

@PFight
Copy link

PFight commented Nov 3, 2017

TypeScript Version: 2.7.0-dev.20171101

Code

https://github.com/PFight/ts-export-bug/tree/master

Expected behavior:

No errors should occur.

Actual behavior:

Compilation error occured. There is workaround (see branch workaround in repo).

Related to #5711

@ghost
Copy link

ghost commented Nov 3, 2017

I don't get any errors compiling that repo with typescript@2.7.0-dev.20171101?

@PFight
Copy link
Author

PFight commented Nov 3, 2017

@andy-ms very strange...

image

@ghost
Copy link

ghost commented Nov 3, 2017

Oh, it looks like git clone https://github.com/PFight/ts-export-bug.git checks out the workaround branch by default.
I don't think this is a bug-bug, but we could improve the error message to tell you that you need an explicit import.

@ghost ghost added Domain: Error Messages The issue relates to error messaging Bug A bug in TypeScript labels Nov 3, 2017
@mhegazy
Copy link
Contributor

mhegazy commented Nov 3, 2017

Already tracked by #9944

@mhegazy mhegazy added Duplicate An existing issue was already created and removed Bug A bug in TypeScript Domain: Error Messages The issue relates to error messaging labels Nov 3, 2017
@typescript-bot
Copy link
Collaborator

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

3 participants