You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running gp rebuild I'm often doing iterations on my configuration. Having to CMD + C to close the terminal, then press up on my terminal, then having to run gp rebuild feels like friction that could be avoided by having the terminal output pause waiting for input, e.g. if the user hits "enter" the gp rebuild command will automatically stop and start. Alternatively, this could be a "y/n" type of input, where the question is "did your configuration complete successfully? y - exit, n - restart". This would be similar ergonomics to the jest testing library, e.g.
› Press Enter to trigger a test run.
The text was updated successfully, but these errors were encountered:
We had bad experience while trying run gp that creates an overlay effect but then it makes links unclickable in VS Code. But maybe it is just an implementation issue.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
When running
gp rebuild
I'm often doing iterations on my configuration. Having to CMD + C to close the terminal, then press up on my terminal, then having to rungp rebuild
feels like friction that could be avoided by having the terminal output pause waiting for input, e.g. if the user hits "enter" thegp rebuild
command will automatically stop and start. Alternatively, this could be a "y/n" type of input, where the question is "did your configuration complete successfully? y - exit, n - restart". This would be similar ergonomics to the jest testing library, e.g.› Press Enter to trigger a test run.
The text was updated successfully, but these errors were encountered: