Committable should act like Evalable when it comes to gisting large output
Open
Nobody has claimed this yet.
committable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
<notviki> Yeah, I wish it didn't make me go to look at gist just to realize there's an error of some sort....
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 locating the Committable and Evalable entry points and compare how each handles large output and gisting. Define completion as Committable producing the same gist behavior as Evalable while making errors visible before sending users to the gist.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100