Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
Currently
amber watcher
stops if an error is found during development, it should stop only if an error is found at beginingA side effect is that an amber background process is never killed so the project keep running silently showing unexpected outputs when you run
amber watch
again.Good (stopping server if there is any error at beginning of development)
Bad (stopping if an error is found during development, server should keep running, waiting for a possible fix)
Alternate Designs
No
Benefits
We avoid the need of executing
amber watch
again and again after every code error. Also we can kill amber server properly avoiding unexpected background processes.Possible Drawbacks
No