graphile-migrate watch allows to run commands after running current migration, but when this command exits with a non-0 code, it just shows the stacktrace instead of stdout/stderr you're usually interested in.
Desired behavior:
Current behavior:
Same thing can somehow be said for graphile-migrate commit, right now it first shows the stacktrace before showing details, including stdout as an escaped string. it would likely be more readable to show stdout/stderr without processing.
Motivating example
The most obvious example is when you want to run tests after current / migrations, you want the exit code to be taken in consideration for CI for example, but at the same time you want a readable output to understand which test failed.
The escape hatch I use for now is to ignore exit code when using watch but not in commit.
Supporting development
I [tick all that apply]:
[] am interested in building this feature myself
[x] am interested in collaborating on building this feature
[x] am willing to help testing this feature before it's released
[ ] am willing to write a test-driven test suite for this feature (before it exists)
Feature description
graphile-migrate watch
allows to run commands after running current migration, but when this command exits with a non-0 code, it just shows the stacktrace instead of stdout/stderr you're usually interested in.Desired behavior:
Current behavior:
Same thing can somehow be said for
graphile-migrate commit
, right now it first shows the stacktrace before showing details, including stdout as an escaped string. it would likely be more readable to show stdout/stderr without processing.Motivating example
The most obvious example is when you want to run tests after current / migrations, you want the exit code to be taken in consideration for CI for example, but at the same time you want a readable output to understand which test failed.
The escape hatch I use for now is to ignore exit code when using
watch
but not incommit
.Supporting development
I [tick all that apply]: