Sieve Editor: Display human readable error message for script errors
Open
Nobody has claimed this yet.
1. to develop
bug
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Thanks for the new sieve editor:) I encountered one minor problem.
Expected behavior
The new sieve editor should give you an easily understandable error message if your script contains errors.
Actual behavior
The editor just displays: Oh snap. Request failed with 500
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 in the Sieve Editor by reproducing the issue with an invalid script and observing the current “Oh snap. Request failed with 500” response. Done means script errors are shown with an easily understandable message instead of the generic request failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100