<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/src, branch main</title>
<subtitle>Rust client for the public CEP API
</subtitle>
<id>http://git.cep.is/rust/atom?h=main</id>
<link rel='self' href='http://git.cep.is/rust/atom?h=main'/>
<link rel='alternate' type='text/html' href='http://git.cep.is/rust/'/>
<updated>2026-07-27T23:33:37Z</updated>
<entry>
<title>Carry the municipality of a CEP that does not exist</title>
<updated>2026-07-27T23:33:37Z</updated>
<author>
<name>Murilo Ijanc</name>
<email>murilo@ijanc.org</email>
</author>
<published>2026-07-27T23:33:37Z</published>
<link rel='alternate' type='text/html' href='http://git.cep.is/rust/commit/?id=487b4c5628c02130580c675925a1d64b09a5f6cb'/>
<id>urn:sha1:487b4c5628c02130580c675925a1d64b09a5f6cb</id>
<content type='text'>
A 404 from the API now brings a "faixa" naming the municipality the CEP
would have belonged to, and NotFound carries it. A CEP that fails is
rarely a random number: it is usually someone who knows the city and
guessed the digits, so naming the city turns a dead end into an answer
the caller can show.

It stays an error. The range it carries is the CEPs that actually exist
there, not the bounds the Correios publish — those start at the very CEP
that just failed — and it is sparse, which is what "ceps" measures. The
field is decoration on a failure, so parsing it is entirely defensive:
absent, null or malformed all yield None rather than costing a clean
not-found.

Breaking: NotFound gained a field, hence 0.2.0.
</content>
</entry>
<entry>
<title>Initial import</title>
<updated>2026-07-26T15:17:46Z</updated>
<author>
<name>Murilo Ijanc</name>
<email>murilo@ijanc.org</email>
</author>
<published>2026-07-26T15:17:46Z</published>
<link rel='alternate' type='text/html' href='http://git.cep.is/rust/commit/?id=4a8c3b675df4b1a6b29904fc2af60605002a7f9e'/>
<id>urn:sha1:4a8c3b675df4b1a6b29904fc2af60605002a7f9e</id>
<content type='text'>
</content>
</entry>
</feed>
