Currently when called by credo it's not possible to specify the migration path because it's hard-coded in relevant_file?/2:
def relevant_file?(path, start_after) do
!String.starts_with?(path, ["deps/", "_build/"]) &&
!String.contains?(path, ["/deps/", "/_build/"]) &&
String.contains?(path, "migrations/") &&
migration_timestamp(path) > start_after
end
This causes an issue because I'm using data migrations (similarly to how it's spelled out here: https://fly.io/phoenix-files/backfilling-data/) that are stored in priv/data_migrations/ and I'd like excellent migrations to ignore them because I do plan to use Repo operations within them (and they have a whole host of other considerations).
Currently when called by credo it's not possible to specify the migration path because it's hard-coded in
relevant_file?/2
:This causes an issue because I'm using data migrations (similarly to how it's spelled out here: https://fly.io/phoenix-files/backfilling-data/) that are stored in
priv/data_migrations/
and I'd like excellent migrations to ignore them because I do plan to use Repo operations within them (and they have a whole host of other considerations).