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 work with a lot of people who are new to coding, and have found that people often get tripped up with reading Ruby exceptions. For example:
While precise, error messages like this don't do a very good job of guiding the reader to how to fix the problems. This PR is a proof-of-concept giving better_errors users a bit of help.
Feedback welcome! In particular, what edge cases am I missing?
P.S. Ideally the message above would read
but that requires some fancy AST parsing (I think).
P.P.S. If others agree it would be useful, I think a good medium-term goal would be to move the backtrace cleaning and hint logic to an external gem, where it could be leveraged by non-web things (like Exercism) that can't use better_errors.