Improve message output for parsing errors
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Ruby
- Stars
- 1.9k
- Forks
- 121
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
While trying to fix a parsing error shown on Packwerk, we had to run rubocop locally since Packwerk did not display any specifics of the error (line number, for example).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a parsing error through Packwerk and trace how the error is reported. The issue provides no file or test entry point; this is done when Packwerk displays useful specifics such as the error line number without requiring RuboCop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100