Canonical UUID text
An identifier has a spelling contract before it has meaning. IdSaffron gives UUID parsing work a project folder and a reviewable model conversation without claiming that syntactic validity proves identity.
import re
UUID_TEXT = re.compile(r"[0-9a-f]{8}(?:-[0-9a-f]{4}){3}-[0-9a-f]{12}")
def uuid_bytes(text):
if not isinstance(text, str) or not UUID_TEXT.fullmatch(text):
raise ValueError("canonical lowercase UUID required")
return bytes.fromhex(text.replace("-", ""))Review before applying
Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.
Connection
Base URL, credentials and a reachable server.
Project
Check all-zero input and hexadecimal letters, rejecting uppercase, braces, misplaced hyphens and surrounding whitespace.
import re
UUID_TEXT = re.compile(r"[0-9a-f]{8}(?:-[0-9a-f]{4}){3}-[0-9a-f]{12}")
def uuid_bytes(text):
if not isinstance(text, str) or not UUID_TEXT.fullmatch(text):
raise ValueError("canonical lowercase UUID required")
return bytes.fromhex(text.replace("-", ""))Agree on identifier representation at the application boundary
IdSaffron gives you a Windows AI coding workspace for examining the small boundary functions that connect larger parts of an application. When identifier handling needs to change, describe which representations are accepted and what downstream code expects. Ask the model to inspect the validator, conversion step and relevant caller together, so an apparently harmless normalization does not quietly widen the input contract.
A task based on uuid_text.py might review acceptance of canonical lowercase UUID text before converting it into bytes. Bring examples that differ in case, separators or surrounding whitespace, and state which should be rejected. Discuss whether normalization belongs before validation or whether the caller must supply the canonical form. Those decisions make the proposed edit specific enough to review against the code.
After the review, run project tests that check both the resulting bytes and the rejected representations. Examine how the application reports invalid identifiers, including paths that previously assumed conversion could not fail. IdSaffron connects to supported OpenAI-compatible or Anthropic endpoints with credentials where required. Unrestricted model options depend on the endpoint you choose; restrictions, available tools and context capacity remain properties of that model and server. The acceptance examples give your coding conversation a stable reference across revisions.
Identifier boundaries that deserve an explicit answer
Should the helper accept uppercase identifiers too?
Decide from the application contract rather than adding permissive behavior automatically. If callers require canonical lowercase text, accepting other forms may hide upstream inconsistency. If normalization is intended, specify its location and test the resulting representation.
Does a valid identifier prove a record exists?
No. Format validation establishes only that the supplied representation meets the expected shape. Existence and authorization belong to separate application checks, so review the consumer before treating successful conversion as permission to access a record.
Why check the bytes as well as accepted text?
Acceptance alone does not prove conversion produces the value the consumer expects. Include known text-and-byte pairs and verify downstream handling, especially if the proposed edit changes serialization or storage boundaries used elsewhere in the project.
What if callers already trim whitespace?
Inspect that behavior before duplicating it. Agree on whether this helper receives normalized input or performs normalization itself. Keeping the responsibility explicit makes rejection rules easier to understand and prevents inconsistent treatment across different call paths.
IdSaffron · Updated 2026-10-25