Improve error message when using --config with a path to a file - #406
Merged
Conversation
Owner
Author
|
@miniBill what do you think? Would this have helped you? If not, do you perhaps have a suggestion on how to improve the wording? |
jfmengels
force-pushed
the
better-error-config-path
branch
from
December 28, 2025 23:16
0f31ffb to
5012daf
Compare
|
I mean, I was able to look at the wrong path and deduce what was wrong but yeah, this is a much better message. In general I think that any time an Elm tool produces a JS stack trace it's a bug (or a stack overflow / OOM) |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #403
Preview in image with colors:
Also adds a test for a similar untested error message.