Changed error message to better reflect the root cause of a failed task #50
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changed error message to better reflect the root cause
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I'm proposing a simple change in the error message below. "Task failed" does not reflect the cause of the problem because the task could not even be found.
Background:
I just invested a couple of ours into finding out what was wrong with my grunt task, before realizing that it didn't fail - because it didn't run in the first place. The real problem was that I used mappings the wrong way. Yet the error message suggests that the problem lies within the grunt task, when it really is about the jit configuration. Because of the confusion I had regarding the "Task failed" error message, I'm now proposing this pull request.