summaryrefslogtreecommitdiffstats
path: root/pubspec.yaml
Commit message (Collapse)AuthorAgeFilesLines
* Name the municipality behind a CEP that does not existHEADv0.2.0mainMurilo Ijanc2026-07-271-1/+1
| | | | | | | | | | | | | | | | | | | A CEP that fails a lookup is rarely a random number: it is usually someone who knows the city and guessed the digits, and the classic guess is the -000 that 957 municipalities never received. The API now attaches a faixa block to the 404 naming the municipality that band belongs to, so the caller can answer "no, but you were looking at Areal/RJ" instead of just "no". It stays an error. Faixa hangs off CepNotFoundException, never off Address, and cepIni/cepFim are the extremes that actually exist in the municipality rather than the range the Correios publish — echoing back the published start would return the very CEP that just failed. The interval is sparse, which is what ceps is for; it is not a list of alternatives. Parsing is deliberately forgiving: a missing, empty or malformed block is null. Losing a clean not-found to a parse error over the hint attached to it would be a bad trade.
* Initial importv0.1.0Murilo Ijanc2026-07-261-0/+17