drud
Error Reporting: Complete
What happened (or feature request):
In https://github.com/drud/ddev-ui/issues/42 we closed out basic error reporting for the alpha release of ddev-ui.
For a later release, we'll want to deal with Complete error reporting. From 42:
- Terminal Output, Normal Mode: Show the normal terminal output that is coming through as ddev CLI is running commands.
- Terminal Output, Verbose Mode: Essentially toggling on/off debug mode for DDEV CLI and reporting that output.
From a visual perspective, we need to do this in a way that doesn't overwhelm the interface, particularly items related to 3 and 4.
Anything else do we need to know:
This needs to be spec'd out.
Related source links or issues:
Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)
The other ticket was really about handling errors within ddev-ui. That's still super important. It wasn't just about handling problems with the project.
I don't think this problem has been well understood. For example, if ddev-ui has an error interacting with ddev, it should say so and not present a blank screen.
@rfay : sounds good, if I misunderstood re: the other ticket, we can either reopen it, or use this one. (The other issue wasn't determined to be a blocker for the v0.4.1 alpha we are trying to get out tomorrow). We need to flesh out details on this one, too.