New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: CLI debug #717

Open

garas opened this issue Dec 10, 2019 · 1 comment

Labels

Member

garas commented Dec 10, 2019 •

edited

It would be useful to debug shells/commands.

When commands finishes, it could print web URL with DebugKit request ID, so all info from executing command could be seen in browser.

Most panels would be still useful, few could be replaced with CLI specific:

Sql Log - most useful to see
Request - could be replaced with parsed arguments/options
Routes - could list all available commands
Cache, Deprecations, Environment, Include, Log, Mail, Packages - same behavior as web
History - CLI requests could be marked differently
Timer - there is no controller events, so only generic duration information
Session, Variables - the only ones I can see no use/replacement in CLI

I'm just unsure how and when DebugKit would inject into app.

garas changed the title ~~Feature~~ Feature: CLI debug

garas added the enhancement label

Member

markstory commented Dec 10, 2019

I'm just unsure how and when DebugKit would inject into app.

We could add and then use events in CommandRunner to attach the panels.

raul338 mentioned this issue

Allow debug kit on cli #887

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment