pub fn parse(value: &str) -> Option<Uuid>Expand description
Parses an id that arrived from outside the process.
None for anything an id column could not hold — a kid a client invented,
a path segment an operator mistyped, a scanner probing /acct/../... Every
caller turns that into the same answer an unknown-but-well-formed id gets,
so no request path grows a “malformed id” case RFC 8555 has no code for.
Deliberately narrower than Uuid::try_parse, which also accepts the
32-character simple form, {braced} and urn:uuid: spellings, and
upper-case hex. Every id this server has ever written came from
Uuid::to_string(), so 36 hyphenated characters is the only shape a column
holds and the only one a URL this server minted can carry. Accepting the
others would start resolving URLs that answer “not found” today, which is a
change of behaviour wearing a refactor’s clothes.