fix(vacaciones): edit and delete vacation ranges
Vacaciones ranges could be created but never edited or removed -- EstadoAlarmas already had crearRangoVacaciones/eliminarRangoVacaciones with no UI affordance reaching them, and no update path at all. Add EstadoAlarmas.editarRangoVacaciones and wire tap-to-edit / swipe-to-delete (with confirmation) onto every range card, mirroring the alarm list's own Dismissible + confirm-dialog pattern exactly. This covers the active-range hero too: a freshly created range is active immediately and only ever renders there, never in the scheduled/past lists, so it needed the same affordances or a user's very first range could never be fixed.
This commit is contained in:
@@ -2078,6 +2078,24 @@ abstract class AppLocalizations {
|
||||
/// **'Nuevo rango de vacaciones'**
|
||||
String get newVacationRangeTitle;
|
||||
|
||||
/// No description provided for @editVacationRangeTitle.
|
||||
///
|
||||
/// In es, this message translates to:
|
||||
/// **'Editar rango de vacaciones'**
|
||||
String get editVacationRangeTitle;
|
||||
|
||||
/// No description provided for @vacationDeleteConfirmTitle.
|
||||
///
|
||||
/// In es, this message translates to:
|
||||
/// **'¿Eliminar rango de vacaciones?'**
|
||||
String get vacationDeleteConfirmTitle;
|
||||
|
||||
/// No description provided for @vacationDeleteConfirmMessage.
|
||||
///
|
||||
/// In es, this message translates to:
|
||||
/// **'Esta acción no se puede deshacer.'**
|
||||
String get vacationDeleteConfirmMessage;
|
||||
|
||||
/// No description provided for @startField.
|
||||
///
|
||||
/// In es, this message translates to:
|
||||
|
||||
Reference in New Issue
Block a user