Support arbitrary knex migration filenames (less opinionated)
Closed this issue · 2 comments
sastraxi commented
Right now it is assumed all migration files start with a \d+_ prefix, but that's just my personal preference (enforcing a complete ordering on migrations forces you to solve the migration ordering problem when you merge branches).
However, we shouldn't be this opinionated. We can support other cases by allowing migration filenames as inputs wherever we currently support numbers.
sastraxi commented
We should assume migrations are lexicographically ordered, and treat the migration names given as prefixes if they are not numbers. If they are numbers, parse the start of the filename as a number and require exact matching.