Closed noisyscanner closed 3 years ago
Describe the bug If I set migrationFileExtension to .ts for TypeScript, I would expect it to load sample-migration.ts instead of sample-migration.js
migrationFileExtension
.ts
sample-migration.ts
sample-migration.js
To Reproduce Steps to reproduce the behavior:
migrations/sample-migration.ts
migrate-mongo-config.js
mirate-mongo create migrationName
Expected behavior Migration to be created using template at migrations/sample-migration.ts
Actual behavior Migration not created using template - the default built-in template is used instead
Additional context Another potential solution could be the abilit to specify sampleMigrationFileName or something in migrate-mongo-config.js
sampleMigrationFileName
Resolved by merging this PR
Describe the bug If I set
migrationFileExtension
to.ts
for TypeScript, I would expect it to loadsample-migration.ts
instead ofsample-migration.js
To Reproduce Steps to reproduce the behavior:
migrations/sample-migration.ts
migrationFileExtension
to.ts
inmigrate-mongo-config.js
mirate-mongo create migrationName
Expected behavior Migration to be created using template at
migrations/sample-migration.ts
Actual behavior Migration not created using template - the default built-in template is used instead
Additional context Another potential solution could be the abilit to specify
sampleMigrationFileName
or something inmigrate-mongo-config.js