germany_plate 0.2.0
germany_plate: ^0.2.0 copied to clipboard
Germany's licence plates for the plate_core library — the country panel, the car spec with its EU stickers, and the German plate validator.
0.2.0 #
- The serial is a register, not four rectangles.
GermanPlates.car's four digits are built byplateRegister(core 0.6.0) — one call stating x 288, pitch 50 — rather than four hand-writtenPlateBoxliterals. The geometry is unchanged to the unit; nothing on a rendered plate moves. - The two district letters and the identifier letter stay literal. Two cells is not a register worth naming, and the identifier letter sits on its own pitch.
GermanPlates.caris nowstatic finalrather thanstatic const: aconstconstructor cannot run a loop.PlateSpecequality is overidalone and astatic finalis initialised lazily once per isolate, so this changes no behaviour — butconst spec = GermanPlates.car;must becomefinal spec = …, as the example now does.- Requires
plate_core: ^0.6.0forplateRegister.
0.1.0 #
First pub.dev release.
-
Depends on the published
plate_core: ^0.1.0(was a siblingpath:dependency). The import ispackage:plate_core/plate_core.dart. No API ofgermany_platechanged. -
Extracted from
plate-core(packageplate_number) at commit86a0999, core version0.1.0(unreleased), as phase P8 of the library split. This is a plain move — no code was rewritten in the transfer. -
Contains Germany's plate data and rule:
GermanyCountry.germany,GermanPlates.car, andGermanPlateValidator. Depends onplate_numberby path and nothing else. -
Owns
assets/de_inspection_sticker.png,assets/de_state_seal.pngandassets/flags/Flag_of_Germany.svg. They moved out of core's bundle in the same commit as theAssetImage/SvgPlateAssetliterals that name them, so there is no revision in which a literal points at a package that does not declare the file. -
Product decision (PLAN.md §6.8):
docs/districts.jsonwas deleted, not wired in. The ~150 realUnterscheidungszeichenit held were unused by any code or pubspec. The validator's district check stays the permissive^[A-ZÄÖÜ]{1,3}$, which is consistent with the demo scope its doc comment has always claimed; keeping a district list accurate is not a promise this package makes. A consumer who wants strict district validation composes their ownPlateValidator.