Just thinking out loud: since this package is based on migrate-mongo (https://github.com/seppevs/migrate-mongo/) I think it's nice to have transition plan to how to switch from migrate-mongo JS to mongo-migrate-ts.
Anyway, for this particular case, during that switch (from migrate-mongo JS to mongo-migrate-ts) I faced the issue of different format of files:
1697236860399_Migration.ts | generated by mongo-migrate-ts
20230105075728-migration.js | generated by migrate-mongo JS
So this is enhancement suggestion: unify format for file naming OR add the config option (migrations.json) to use specific time format.
Just thinking out loud: since this package is based on migrate-mongo (https://github.com/seppevs/migrate-mongo/) I think it's nice to have transition plan to how to switch from migrate-mongo JS to mongo-migrate-ts.
Anyway, for this particular case, during that switch (from migrate-mongo JS to mongo-migrate-ts) I faced the issue of different format of files:
1697236860399_Migration.ts
| generated by mongo-migrate-ts20230105075728-migration.js
| generated by migrate-mongo JSSo this is enhancement suggestion: unify format for file naming OR add the config option (
migrations.json
) to use specific time format.📓 The difference of timestamps: