Its kinda sketchy that drifter-postgresql just uses putStrLn to log skipped messages or failed migrations rather than potentially integrating with the user's logging system, but it isn't clear how that should work anyways. While we are printing to stdout, we may as well print the name of a migration when we are running it to help with debugging if the user's migration code fails.
Its kinda sketchy that drifter-postgresql just uses putStrLn to log skipped messages or failed migrations rather than potentially integrating with the user's logging system, but it isn't clear how that should work anyways. While we are printing to stdout, we may as well print the name of a migration when we are running it to help with debugging if the user's migration code fails.