Needs nonzero exit status on error
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Expected behavior:
On error, exits with a nonzero error code.
Actual behavior:
Exits with zero regardless of success or failure.
Why this is a problem:
Causes issues with scripts which rely on the exit status of gput (e.g. as part of a pipeline), as they cannot easily determine whether it has failed without additional processing of the JSON output.
Contributor guide
No contributing guide indexed for this repository
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 gput's command-line entry point and its error-handling path. Check how successful and failed operations currently finish, then verify that success and failure produce the expected exit statuses for scripts and pipelines, while preserving the JSON output behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100