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
Similar to this comment, I've run into some headaches caused by the fact that errors are printed to STDOUT not STDERR. Nothing I can't work around (yet) but it's something I have to take into account and handle when working on tooling that uses suitecloud.
I have also noticed that not all commands exit with non-zero exit codes on error: suitecloud project:validate does but suitecloud project:deploy does not, at least not if the error happened during validation. This would make developing tooling that uses deploy considerably more difficult.
If there isn't good reason not to, it would be helpful to have errors printed to STDERR and for all commands to only exit with 0 if they were successful.
The text was updated successfully, but these errors were encountered:
Similar to this comment, I've run into some headaches caused by the fact that errors are printed to STDOUT not STDERR. Nothing I can't work around (yet) but it's something I have to take into account and handle when working on tooling that uses
suitecloud
.I have also noticed that not all commands exit with non-zero exit codes on error:
suitecloud project:validate
does butsuitecloud project:deploy
does not, at least not if the error happened during validation. This would make developing tooling that usesdeploy
considerably more difficult.If there isn't good reason not to, it would be helpful to have errors printed to STDERR and for all commands to only exit with 0 if they were successful.
The text was updated successfully, but these errors were encountered: