π§ Schema Compatibility Fixes - v0.9.8
π§ Critical Schema Compatibility Fixes
This release resolves critical GraphQL schema compatibility issues that were causing service failures.
β Major Fixes
- Fixed TransactionService.get_transaction_categories: Removed duplicate method, updated to use correct
GetCategoriesquery with proper fragment structure - Fixed BudgetService.get_budgets: Updated to use
Common_GetJointPlanningDatawith requiredDate!parameters and intelligent date defaults - Fixed AccountService.get_accounts: Added missing
typeandsubtypefields to GraphQL query
π Health Check Results
- Schema Errors: Reduced from 2 to 0 β
- Service Status: Improved from UNHEALTHY to DEGRADED β
- All "Something went wrong" GraphQL errors resolved β
ποΈ Cleanup
- Removed non-working schema introspection system (MonarchMoney disables introspection for non-admin users)
- Operation health check is now the primary schema monitoring system
π Impact
- TransactionService, BudgetService, and AccountService now work reliably
- Services use GraphQL queries that match current MonarchMoney API schema
- Improved error handling and diagnostics
π Related Issues
- Resolves #33 - GraphQL Schema Errors Detected
- Thanks to @pazwicker for the backwards-compatible transaction enhancements in #32
π Migration Notes
No breaking changes - all existing code continues to work as before.
Generated with automated schema monitoring and health checking