Skip to content

Add adapter fixtures for provider events we do not cover yet #3

Description

@nullarch

Adapters normalise provider hook payloads into the canonical Event (RFC 0001). Every event name an adapter handles must have a fixture plus a golden normalised envelope, so a provider changing its payload shape breaks a test rather than silently losing data.

What to do

Pick a provider (claude_code, codex, cursor, gemini_cli), find an event name that crates/attemptdb-adapters/src/<provider>.rs handles but fixtures/providers/<provider>/ has no fixture for, and add one.

  • Fixtures are synthetic or scrubbed: no real prompts, commands, paths, tokens, repository names. Sanitise paths to /home/dev/… and repos to example/project, and mark authored fixtures with _fixture_note. See the "Fixtures rule" section of CONTRIBUTING.md.
  • Regenerate goldens with UPDATE_GOLDEN=1 cargo test -p attemptdb-adapters and review the diff — it is the actual review artifact.

Done when

cargo test -p attemptdb-adapters passes with the new case, and the privacy canary tests stay green.

Good first issue, and the best way to learn the event model. Comment which provider and event you are taking so two people do not pick the same one.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    adaptersProvider adapters and fixturesgood first issueGood for newcomers

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions