Rider displays rollback warning when EF Core migration lacks a Down method

Rider’s Database tool window lets developers apply and roll back EF Core migrations directly from the IDE. When a migration includes a Down method, the rollback executes without warning; if the Down method is missing or contains irreversible operations, Rider shows a warning that data loss may occur and requires manual confirmation.

The design question is whether Rider should automatically generate a Down migration when none exists, block the rollback action until a Down method is provided, or keep the current warning‑and‑confirmation approach. This decision must balance safety against workflow convenience and align with EF Core best practices.

Should Rider prompt to create a Down migration automatically? Should Rider disable the rollback action until a Down method is present? What behavior best protects data while preserving developer productivity?