Hagernesh b616f520ae feat(fleet): validate vehicle plate numbers against a letters-and-digits format ...

Plate, power-plate and trailer accepted any free text — a vehicle could be
saved with a plate of "assadasd". They must be letters, a hyphen, then digits,
like ET-9875 or AA-8642.

The server now enforces it on CreateVehicleDto (and UpdateVehicleDto via
PartialType): each plate is trimmed and upper-cased, then matched against
^[A-Z]{2,3}-\d{2,6}$, so "et-9875" is accepted and stored as ET-9875 while an
empty optional trailer/power plate still passes.

The fleet form gains the same check inline: FleetFormFieldDef takes an optional
pattern, the dialog tests it on submit against the upper-cased value, and the
vehicle config points plate and trailer at a regex that mirrors the server's.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-21 11:03:40 +00:00

..

backoffice

feat(fleet): validate vehicle plate numbers against a letters-and-digits format

2026-07-21 11:03:40 +00:00

portal

Implement intercity document handling and rejection notes for contracts

2026-07-21 10:20:36 +00:00