Is your feature request related to a problem? Please describe.
It's difficult to get information on some type of errors.
Describe the solution you'd like
We need to curate the error messages to be more precise and offer more details.
Describe alternatives you've considered
We could also just to add stack traces to our errors.
Although it is somewhat a solution, I really don't like this because we can do better.
Since we have clear separation between state and logic, it should be very easy for us to validate every part of our state correctly and provide proper explanation for the errors we create.
Additional context
There are some edge cases where we don't have that much control over error messages, specifically exec commands that take over the cli completely, like dev and package-watch modes, we shouldn't bother validating those atm, it's out of scope.
Is your feature request related to a problem? Please describe.
It's difficult to get information on some type of errors.
Describe the solution you'd like
We need to curate the error messages to be more precise and offer more details.
Describe alternatives you've considered
We could also just to add stack traces to our errors.
Although it is somewhat a solution, I really don't like this because we can do better.
Since we have clear separation between state and logic, it should be very easy for us to validate every part of our state correctly and provide proper explanation for the errors we create.
Additional context
There are some edge cases where we don't have that much control over error messages, specifically exec commands that take over the cli completely, like
devandpackage-watchmodes, we shouldn't bother validating those atm, it's out of scope.