From c4032605e0833a4c74d9bf58e679a83349ce9fb1 Mon Sep 17 00:00:00 2001 From: Murilo Ijanc Date: Mon, 27 Jul 2026 20:37:47 -0300 Subject: Name the municipality behind a CEP that does not exist MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A CEP lookup that fails is rarely a random number: it is usually someone who knows the city and guessed the last digits, most often the -000 that 957 municipalities never received. The API now answers those 404s with a `faixa` naming the municipality the number would have belonged to and the first and last CEP that really exist there, so the shopper can be told "esse número seria de Areal/RJ" instead of a bare "não encontrado". It stays an error. The address does not exist, so no field is filled from `faixa` — quietly writing the city of a CEP that does not exist would produce a wrong address, which is worse than an empty form. Only the wording of the message changes. The range is sparse (Areal has 118 CEPs over some 4,900 numbers), so it is shown as a hint of where to look, never as a list to pick from. Parsing is defensive throughout: a body that is not JSON, a `faixa` that is not an object, a missing localidade or uf, a malformed range — each falls back to the message shipped before, and none of it can throw. --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'package.json') diff --git a/package.json b/package.json index 798ab4b..a242375 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "cepis-autofill", - "version": "0.1.0", + "version": "0.2.0", "description": "Drop-in address autofill widget for Brazilian checkouts, on top of the CEP API at cep.is", "keywords": [ "cep", -- cgit v1.3