fix(freight-backoffice): render wagon transfer reason as sanitized HTML in a modal

This commit is contained in:
Marshal
2026-08-10 14:02:13 +00:00
parent 573e777e8f
commit e29e3ff837
6 changed files with 108 additions and 11 deletions

View File

@@ -510,6 +510,8 @@ export class TrainBuilderService {
trainId: null,
sequenceNumber: null,
status: WagonStatus.Available,
importTrainNumber: null,
exportTrainNumber: null,
});
await this.resequenceWagons(manager, train.id);
await this.syncLiveScheduleAfterConsistChange(
@@ -544,6 +546,8 @@ export class TrainBuilderService {
trainId: null,
sequenceNumber: null,
status: WagonStatus.Maintenance,
importTrainNumber: null,
exportTrainNumber: null,
});
// Audit row: which train it came off and when. The wagon does not change
// yard here, so from/to are the same — the ledger is the wagon's history
@@ -761,7 +765,13 @@ export class TrainBuilderService {
.getRepository(Wagon)
.update(
{ trainId: train.id },
{ trainId: null, sequenceNumber: null, status: WagonStatus.Available },
{
trainId: null,
sequenceNumber: null,
status: WagonStatus.Available,
importTrainNumber: null,
exportTrainNumber: null,
},
);
await manager.getRepository(TrainLocomotive).delete({ trainId: train.id });
await manager.getRepository(Train).remove(train);
@@ -1021,6 +1031,10 @@ export class TrainBuilderService {
trainId: train.id,
sequenceNumber: sequence,
status: WagonStatus.Assigned,
// Wagon inherits the train's run numbers on coupling — no per-wagon
// number entry, they ride whatever numbers the train was built with.
importTrainNumber: train.importTrainNumber,
exportTrainNumber: train.exportTrainNumber,
});
}
return toAttach;