pingcap / pingcap/tiup

playground: playground should not take over console

Open
#832 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

category/usability status/discuss status/wontfix
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

IMO, it is more user friendly for the playground to run as a background process. Then the user can use the playground without starting a new terminal. The playground should give info for how to stop the playground along with the other info it gives on startup.

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.

Research direction

Start from the playground command and its startup output. Trace how the playground process currently occupies the console, then determine the existing stop mechanism before changing it to run in the background. Done means users can keep using the same terminal and startup output explains how to stop the playground.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.