Skip to content

feat(ledger): event blocks carry the document they rest on - #247

Merged
jfrench9 merged 1 commit into
mainfrom
feature/event-document-id
Oct 10, 2026
Merged

jfrench9 merged 1 commit into
mainfrom
feature/event-document-id

Conversation

@jfrench9

Copy link
Copy Markdown
Member

Summary

get_event_block and list_event_blocks now select documentId, so their models carry the stored document an event cites. Setting the field already works through update_event_block: document_id, where "" detaches.

This waits on robosystems #1769, which adds EventBlock.documentId to the GraphQL schema. These queries select the field, so against a server without it they fail validation. Per the client contract, open it ready and release it once #1769 is deployed (or with it).

Contract tier

Additive to the stable tier: a new nullable field on two facade return types. That makes it a client minor or patch.

Test plan

  • schema.graphql refreshed from a local stack serving #1769 (one line, documentId: String), and the GraphQL models regenerated.
  • Facade tests: get_event_block returns document_id, and the list fixture carries it.
  • just test-all passes: 673 tests, ruff and basedpyright clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01AQkGGPDmpba9eBV9PkLTfv

get_event_block and list_event_blocks select documentId, so a caller can
see the bill, receipt or statement an event cites. Set it through
update_event_block's document_id ("" detaches). schema.graphql refreshed.

Claude-Session: https://claude.ai/code/session_01AQkGGPDmpba9eBV9PkLTfv
@jfrench9
jfrench9 merged commit b48c4ff into main Oct 10, 2026
4 checks passed
@jfrench9
jfrench9 deleted the feature/event-document-id branch October 10, 2026 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant