luckyframework / luckyframework/lucky
Store the class, file, and line number of a before/after declaration
Open
Nobody has claimed this yet.
improve error experience
- Dominant language
- Crystal
- Stars
- 2.7k
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
Then display it when halted. Help people track down where a pipe was added
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
Locate the before/after declaration handling and the code that halts a pipe, then trace how declarations are represented and reported. The work is done when the halted output identifies the declaration's class, file, and line number so the pipe's origin can be found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100