@@ -279,10 +279,15 @@ public actor DatabaseMigrations {
279279 static var ignoreUnknownMigrations : Self { . init( rawValue: 1 << 0 ) }
280280 /// Remove database entry for migrations we don't know about
281281 static var removeUnknownMigrations : Self { . init( rawValue: 1 << 1 ) }
282- /// Disable the reverting of migrations that follow the revert of an applied migration that is
283- /// not in the migration list
282+ /// Disable the reverting of migrations that follow an applied migration that is inconsistent
284283 ///
284+ /// The default action is to revert all migrations after finding one that is inconsistent. The
285+ /// logic behind this is that removing that migration but not the following migrations will
286+ /// leave the database structure in indeterminate state. But this is a destructive action and
287+ /// you can disable this with this option.
285288 ///
289+ /// Using this option means `revertInconsistent` cannot fix the migration list if the order of
290+ /// migrations has changed.
286291 static var disableRevertsFollowingRevert : Self { . init( rawValue: 1 << 2 ) }
287292 }
288293
@@ -291,7 +296,7 @@ public actor DatabaseMigrations {
291296 /// This will revert any migrations in the applied migration list after an inconsistency has been found in
292297 /// list eg a migration is missing or the order of migrations has changed. This is a destructive action
293298 /// so it is best to run this with dryRun set to true before running it without so you know what migrations
294- /// it will revert.
299+ /// it will revert. You can control this using the options parameter.
295300 ///
296301 /// For a migration to be removed it has to have been registered either using
297302 /// ``DatabaseMigrations/add(_:skipDuplicates:)`` or ``DatabaseMigrations/register(_:)``. If a migration name
0 commit comments