Closed mnapoli closed 2 years ago
The proposed solution is great, however, we also have different error scenarios - the ones that happen as a part of executing a command for a specific service that fails, the example below:
Do you think we should improve this scenario in some way as well?
I think for these errors we're kinda good.
Ideally there shouldn't be an "Error:" prefix (to be consistent with other error messages, and keep the dynamic output short). Maybe that's a detail we can improve?
We want to format errors closer to the Serverless Framework formatting.
Current
Target
Example of a Serverless Framework init error:
we should follow that same approach:
Error:
in red on its own lineHere's what the top block could contain for now: