Output message in console when error is resolved

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
cli

Research direction

Start by tracing the dev/sandbox rebuild status handling and the console output path. Reproduce a build error, fix it, and verify that transitioning to a successful server state prints an explicit success message while existing error output remains intact.

Written by the indexing model from the issue text.

Description

enhance dev/sandbox feature request: currently, when sandbox is running, it produces no output unless there is a build error. this is probably smart. however i've noticed that after i fix the build error, since there is no output, every time i tab back into my sandbox terminal, the only thing i see is an error message, and it leaves me wondering what state the sandbox is in. (is it errored? is it now building correctly?). it would be nice, from my perspective, for a message to be printed out in the case where we switch from a broken state to a successful server state. Something like [checkmark] App successfully rebuilt, maybe. it would give me peace of mind when i go back to see the last known state explicitly.

Dominant language
JavaScript
Stars
2
Forks
2
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from enhance-dev/cli

All issues in enhance-dev/cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.