summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Carry the municipality of a missing CEP on not_foundHEADv0.2.0mainMurilo Ijanc2026-07-277-13/+278
| | | | | | | | | | | | | | | | | A CEP that fails is rarely a random number: it is someone who knows the city and guessed the digits, and the classic guess is the -000 that 957 municipalities never received. The API now answers that 404 with an optional faixa block naming where the CEP would have been, so a caller can turn "CEP does not exist" into something the user can act on. It hangs off the error, never off an address: the lookup still failed. Parsing gives up quietly at every step — no block, a block that is not an object, one without a municipality to name — because a broken piece of context must not turn a clean not-found into a parse failure. cep_ini and cep_fim are the CEPs that exist, not the range the Correios publish, and the interval between them is sparse; ceps is what keeps the pair from being read as a list of valid CEPs.
* Initial importv0.1.0Murilo Ijanc2026-07-2613-0/+2494