Closed JudahGabriel closed 7 months ago
Since migrations are talking to a remote service, it seems like migrations should all return Task, rather than void.
And that MigrationRunner.Run should actually be MigrationRunner.RunAsync.
This would let migration code use async/await and some of the APIs that are more natural in Raven; no need to Task.Wait or other kludges.
One problem with this is that migrations are usually run in the Startup/Program code, which is usually not async.
And given that migration code is run on startup, asynchrony isn't very important. Closing.
Since migrations are talking to a remote service, it seems like migrations should all return Task, rather than void.
And that MigrationRunner.Run should actually be MigrationRunner.RunAsync.
This would let migration code use async/await and some of the APIs that are more natural in Raven; no need to Task.Wait or other kludges.