Is your feature request related to a problem? Please describe.
If a project uses Javascript and then later converts to Typescript, the storage of the file extension in the database for checking if a migration was run creates inconsistencies.
Describe the solution you'd like
There's no particular reason the extension should have been included in the stored filename IMO, however it'll be hard to remove for compatibility. Suggest adding an option to the migration config (e.g. "--ignore-extension") that ignores the extension that is stored when checking if the file was run.
Is your feature request related to a problem? Please describe. If a project uses Javascript and then later converts to Typescript, the storage of the file extension in the database for checking if a migration was run creates inconsistencies.
Describe the solution you'd like There's no particular reason the extension should have been included in the stored filename IMO, however it'll be hard to remove for compatibility. Suggest adding an option to the migration config (e.g. "--ignore-extension") that ignores the extension that is stored when checking if the file was run.