You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: