Changes between Initial Version and Version 1 of Ticket #23728
- Timestamp:
- Oct 28, 2014, 8:11:06 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #23728 – Description
initial v1 9 9 1. Enable this always. This is very simple to implement and easy to understand. Good unixy tools use error codes extensively to signal errors. This may be surprising behaviour when compared to `grep` though, and breaks backwards compatibility in a minor way. 10 10 2. Enable this when the `--dry-run` flag is enabled. Now this flag can be used to check for migrations that need to be created both visually via the printed text, and composed in shell commands. 11 3. Add a new flag `-e`/`--exit` (or similar). The sole purpose of this flag would be to exit with `1` when no migrations were found. 11 3. Add a new flag `-e`/`--exit` (or similar). The sole purpose of this flag would be to exit with `1` when no migrations were found. This could be combined with --dry-run to just check for migrations that need to be made. 12 12 4. Add a new flag `-q`/`--quiet` that copies the behaviour of `grep`s `-q`/`--quiet` flag: silences output and exits with `1` when no migrations were found. This duplicates functionality though, as logging can be silenced using `-v0` already. 13 13 14 My personal preference is for option 2. I was surprised when enabling `--dry-run` did not signal its result via the exit code. 3 would be the cleanest and most composable option , as 4 could be emulated using `-ev0`.14 My personal preference is for option 2. I was surprised when enabling `--dry-run` did not signal its result via the exit code. 3 would be the cleanest and most composable option. 15 15 16 16 I will implement this change using 2, unless other people have opinions on the matter.