Aglet

Triage an API enum value expansion

An unfamiliar enum can be an additive value, a spelling change, bad data, or a command the client must not guess. Freeze one response and record raw value, resource state, parser branch, and local outcome. Compare a known neighboring value before changing exhaustive code.

Establish what is happening

  1. Capture the raw value

    Record endpoint, resource identifier, raw enum token, response version, client revision, and selected local branch without sensitive payloads. Note whether parsing failed, defaulted, or continued. Keep the token exact for a contract comparison.

  2. Compare known neighbors

    Run a known success, known pending, known failure, and the unfamiliar value through the same mapper. Compare storage, display, and irreversible actions. A fallback that looks friendly can still misclassify a state or trigger work.

  3. Bound enum consumers

    Group unknown values by field, endpoint, version, client, and downstream action. Separate additive value, typo, malformed input, and branch exhaustiveness. If source meaning is unavailable, mark it unknown instead of naming the value from its spelling.

What to carry forward

Triage ends with the raw token, first parser or branch boundary, affected consumers, and evidence gap. Keep unknown states visible. Route contract, parser, and action questions separately. Do not infer meaning from token spelling. Keep unknown state separate from known success.

Technical background: Project documentation on GitHub.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow