diff options
| author | Murilo Ijanc <[email protected]> | 2026-07-27 20:37:09 -0300 |
|---|---|---|
| committer | Murilo Ijanc <[email protected]> | 2026-07-27 20:37:09 -0300 |
| commit | a891657aa43d2aba06a6347dd2f94edd19afd6ba (patch) | |
| tree | b6369ed2c8485455f9c1aa707c1cd287cb8e7065 /source/cepis/package.d | |
| parent | 794f28199a4dde9d18ec711864336c96c58bb422 (diff) | |
| download | d-0.2.0.tar.gz | |
A 404 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 to the
not-found body naming the municipality that owns the range, so the caller
can say "no such CEP, but that range is Areal/RJ" instead of only "no".
It stays an error. Faixa hangs off CepNotFoundException, never off
Address, and parsing is deliberately lenient: an absent, malformed or
unnamed block yields a null Nullable, so reading the extra context can
never cost the caller the answer it already had.
cep_ini and cep_fim are the smallest and largest CEP that actually exist
there, not the bounds the Correios publish, and the range between them is
sparse — hence ceps, so nobody mistakes the pair for a list.
Diffstat (limited to 'source/cepis/package.d')
| -rw-r--r-- | source/cepis/package.d | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/source/cepis/package.d b/source/cepis/package.d index 073d377..9a8c433 100644 --- a/source/cepis/package.d +++ b/source/cepis/package.d @@ -41,6 +41,10 @@ * if (error.retriable) reschedule(); // network, server, rate limit * --- * + * A not-found sometimes knows where the CEP $(I would) have been — see + * $(D CepNotFoundException.faixa) and $(D Faixa). That is context for the + * error, never an address. + * * Note on field names: the API surface is English, but the $(B data fields keep * the API's own Portuguese names) ($(D logradouro), $(D bairro), * $(D localidade)). What you read in the JSON is what you access on the value. |