<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lua/cepis-0.1.0-1.rockspec, branch v0.2.0</title>
<subtitle>Lua client for the public CEP API
</subtitle>
<id>http://git.cep.is/lua/atom?h=v0.2.0</id>
<link rel='self' href='http://git.cep.is/lua/atom?h=v0.2.0'/>
<link rel='alternate' type='text/html' href='http://git.cep.is/lua/'/>
<updated>2026-07-27T23:33:25Z</updated>
<entry>
<title>Carry the municipality of a missing CEP on not_found</title>
<updated>2026-07-27T23:33:25Z</updated>
<author>
<name>Murilo Ijanc</name>
<email>murilo@ijanc.org</email>
</author>
<published>2026-07-27T23:33:25Z</published>
<link rel='alternate' type='text/html' href='http://git.cep.is/lua/commit/?id=58dbe934a90c1eda8e76cd218a413f01a4d9b11d'/>
<id>urn:sha1:58dbe934a90c1eda8e76cd218a413f01a4d9b11d</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Initial import</title>
<updated>2026-07-26T15:42:08Z</updated>
<author>
<name>Murilo Ijanc</name>
<email>murilo@ijanc.org</email>
</author>
<published>2026-07-26T15:42:08Z</published>
<link rel='alternate' type='text/html' href='http://git.cep.is/lua/commit/?id=7fd555fcaf4304cb0dff3e8f5661565c3618299e'/>
<id>urn:sha1:7fd555fcaf4304cb0dff3e8f5661565c3618299e</id>
<content type='text'>
</content>
</entry>
</feed>
