Skip to content

Feature request: format compile errors by files in src #1504

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
matt-erhart opened this issue Jul 31, 2016 · 2 comments
Closed

Feature request: format compile errors by files in src #1504

matt-erhart opened this issue Jul 31, 2016 · 2 comments
Labels
feature Issue that requests a new feature

Comments

@matt-erhart
Copy link

When I get a compile error, I typically want to know where the error is in files in src, not the cascade into the libraries. Novices sometimes don't even know there is useful information in the 'ng serve/build' terminal. I think errors could be understood a lot easier if the errors were formatted something like this:
ng build ->
Typical Error Message:
...business as usual...

Compile Errors from src files:
[file_name] [line number] [error message]

I think this would help everyone search out the most useful parts of the message, and help novices discover important information.

@filipesilva filipesilva added the feature Issue that requests a new feature label Aug 10, 2016
@filipesilva
Copy link
Contributor

#1455 made these better, since we use the webpack report format.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Issue that requests a new feature
Projects
None yet
Development

No branches or pull requests

2 participants