bug: missing migration file does not cause a failure

[jousby]

I've got the following code for running a test of my migrations:

    it(
      'should apply the placeholder 1.0.0 migration',
      async () => {
        const migrate = new Migrate(
          {
            client: localDynamoDB.dynamodbClient,
            name: tableName,
            schema: AssetSchema_1_0_0,
            partial: true,
          },
          { dir: './src/dao/migrations' },
        )
        await migrate.init()
        await migrate.apply('up', '1.0.0', { dry: false })
      },
      timeoutMilliseconds,
    )

when

        await migrate.apply('up', '1.0.0', { dry: false })

runs it goes looking for a file called 1.0.0.js in ./src/dao/migrations. If this file is not present the apply command returns successfully after logging:

   [
     'Run migration "up"',
     { action: 'up', versions: [ ], version: '1.0.0' }
   ]

I think a more helpful response here is that if you try to apply a '1.0.0' migration and it doesn't find a file or inline migration for that version it should throw.

[mobsense]

The apply routine for up and down was applying all intermediate migrations and was stopping when no more migrations were found for the target version. It was not checking if that version was actually found.

Will apply a fix for this.

thanks for reporting