Skip to content

Duplicate errors #89

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

Closed
hdave opened this issue Sep 26, 2016 · 6 comments
Closed

Duplicate errors #89

hdave opened this issue Sep 26, 2016 · 6 comments
Milestone

Comments

@hdave
Copy link

hdave commented Sep 26, 2016

I can replicate this with the ng2 tour of heros source code. Essentially, I get an error in hero.service.ts. Everytime I edit a related file and save (build on save is true), the errors for hero.service.ts are doubled. Then tripled, etc.

Here is a screenshot of what is happening. Should I open a separate issue on why the error was there in the first place? The code runs perfect and compiles from the command line without error. I have the plugin configured to use my external npm (6.x) and typescript (2.0.3)

ts errors

@angelozerr
Copy link
Owner

angelozerr commented Sep 26, 2016

Let me try your sample. For the moment I have none idea why you have this problem. Could you share your project please.

@hdave
Copy link
Author

hdave commented Sep 27, 2016

I don't have a way to share my project, but you can get the exact same code here:

https://github.com/johnpapa/angular2-tour-of-heroes

@angelozerr
Copy link
Owner

@hdave I cannot reproduce your problem -(

The only problem that I see is if you run the lauch "Compile" and you save your file just after. There are some problems sometimes (I will try to discover this problem).

@angelozerr
Copy link
Owner

@hdave please answer me to my question in order to I investigate to your problem. Thanks!

@probert94
Copy link
Contributor

@angelozerr the problem is probably the same as in #132 ...
As this one is opened since a very long time and a lot of things changed since then, I guess this one can be closed?

@angelozerr angelozerr added this to the 1.3.0 milestone Jun 29, 2017
@angelozerr
Copy link
Owner

Yes sure @Springrbua

@hdave if you have again the problem, please reopen it. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants