[feature request] build chain error handling

[jgw96]

From @wzr1337 on June 28, 2016 21:49

I just had an issue with code that did not compile because I wanted to assign a number to a string. Typescript did not compile. This caused to browser code I was running to remain the same. Unfortunately, I did not notice the error in the shell, because it was hidden behind the editor.

I would strongly recommend to catch any build error, pipe it into a static page and refresh the app in the browser with just the error page. This way, developers will be immediately aware of errors, that prevent code from being actually build and refreshed in the browser. Angular.cli for examples does catch all kinds of errors and puts them on the error age they show instead of the app in case of any errors.

The errors to catch would be any kind of .ts and *.scss and so on.

Best regards

Copied from original issue: ionic-team/ionic-framework#7105

[jgw96]

Hello, thanks for opening an issue with us! Since this is a feature request that would be implemented by the ionic-cli and not the framework I will be moving this issue to the ionic-cli repo. Thanks for using Ionic!

[wzr1337]

Well, you are right, thanks!

On Tuesday, June 28, 2016, Justin Willis notifications@github.com wrote:

Hello, thanks for opening an issue with us! Since this is a feature
request that would be implemented by the ionic-cli and not the framework I
will be moving this issue to the ionic-cli repo. Thanks for using Ionic!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1127 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ADiF7Rxmq7zsLS7Ga4loynXm-0BLFjWRks5qQZeagaJpZM4JAk1c
.

• Patrick
  (Mobile)