Skip to content

feat: add file report and transition filing status operations#106

Merged
jfrench9 merged 1 commit intomainfrom
feature/block-viewers
Apr 26, 2026
Merged

feat: add file report and transition filing status operations#106
jfrench9 merged 1 commit intomainfrom
feature/block-viewers

Conversation

@jfrench9
Copy link
Copy Markdown
Member

Summary

Introduces two new ledger operations — File Report and Transition Filing Status — to the RoboSystems client SDK. This includes new API operation classes, request models, GraphQL query definitions, and ledger client integration.

Key Accomplishments

New API Operations

  • op_file_report.py — Implements the file report operation against the RoboLedger extension API, enabling clients to programmatically file reports through the ledger system.
  • op_transition_filing_status.py — Implements the transition filing status operation, allowing clients to move filings through their lifecycle states.

New Request Models

  • FileReportRequest — Typed model encapsulating the parameters needed to file a report.
  • TransitionFilingStatusRequest — Typed model encapsulating the parameters for transitioning a filing's status.

Client & Query Integration

  • Extended LedgerClient with convenience methods for both new operations, maintaining a consistent API surface for consumers.
  • Added corresponding GraphQL query definitions in the ledger query module to support the new operations.
  • Updated models/__init__.py to export the new request models for public use.

Breaking Changes

None. This is a purely additive feature — no existing APIs, models, or behaviors are modified in a breaking way.

Testing Notes

  • Verify that file_report and transition_filing_status methods on LedgerClient correctly construct and execute their respective operations.
  • Validate request model serialization and field validation for both FileReportRequest and TransitionFilingStatusRequest.
  • Test error handling for invalid inputs and unexpected API responses from both operations.
  • Confirm the new GraphQL queries are well-formed and accepted by the target ledger API.

Infrastructure Considerations

  • No new dependencies are introduced; the implementation follows established patterns in the existing codebase.
  • The new operations rely on the existing RoboLedger extension API infrastructure — ensure the target environment supports the corresponding GraphQL endpoints.
  • Consider adding these operations to any automated integration or contract test suites that cover the ledger client.

🤖 Generated with Claude Code

Branch Info:

  • Source: feature/block-viewers
  • Target: main
  • Type: feature

Co-Authored-By: Claude noreply@anthropic.com

@jfrench9 jfrench9 merged commit 7f6ba76 into main Apr 26, 2026
1 check passed
@jfrench9 jfrench9 deleted the feature/block-viewers branch April 26, 2026 04:49
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