Description
I'd like to give the tool more options for a leaner output similar to other test frameworks to set the focus on errors and not good migrations.
What I ideally want in the very first iteration:
$ migrate --path /some/app --env staging --format dots up
....F..F
8 Migrations/Actions:
6 Passed - 2 Failed
Failure/s:
FAILED_MIGRATION_FILEPATH_1:
{Stacktrace - which will usually contain the sql + what is wrong}
{Filepath of failed migration + line location?}
FAILED_MIGRATION_FILEPATH_2:
{Stacktrace - which will usually contain the sql + what is wrong}
{Filepath of failed migration + line location?}
Or to slice it smaller and make a PR less complex: Just print the exceptions.
Something like that. I'm not sure how to include hooks in the output yet - I'd just add them to the total count and treat them as migrations as well. So maybe "8 Migrations" is not the correct naming.
Some input about using a strategy for that:
Ref: #104
h3adache: In the future I would love to see the console writing be split out into a strategy so that you can use color console/logging as a strategy across not just the final error and status lines but this is a great feature on it's own.
@h3adache Could you add more input how that strategy would look like? Or what your idea behind it is?