improve behaviour when there's a shadowlisp error
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 458
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Shadowenv should behave better when there's a shadowlisp error:
Rather than claiming activation, we should probably suppress the activation message, and maybe even reset the environment to the root/undone state.
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 the ShadowLisp error shown in the attached screenshot and tracing the activation path that reports success. The issue is done when an error no longer claims activation and the environment is reset to the root or undone state, if that behavior is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100