Skip to content

feat(graphql): extract subscription error policy#866

Draft
stdevi wants to merge 4 commits into
masterfrom
refactor-graphql-service
Draft

feat(graphql): extract subscription error policy#866
stdevi wants to merge 4 commits into
masterfrom
refactor-graphql-service

Conversation

@stdevi

@stdevi stdevi commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

No description provided.

Stanislav Deviatykh and others added 2 commits June 30, 2026 15:37
Move QminderGraphQLError and the non-retryable subscription-error
classification into graphql-error.ts (re-exported from graphql.service for
backward compatibility). Behaviour-preserving; protocol-agnostic pieces the
library transport will reuse. No test changes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Move the retryable-subscription-error state machine out of GraphqlService into
a transport-agnostic, callback-based RetryableSubscriptionErrorPolicy (retry /
fail actions supplied by the service). Behaviour-preserving — same batch retry,
5-attempt limit, 500ms success grace, and haveAnyRetryableSubscriptionsErrored
semantics. No test changes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@stdevi stdevi changed the title Refactor graphql service feat(graphql): extract subscription error policy Jun 30, 2026
Stanislav Deviatykh and others added 2 commits June 30, 2026 16:34
Move the retryable-subscription-error state machine out of GraphqlService into
a transport-agnostic, callback-based RetryableSubscriptionErrorPolicy (retry /
fail actions supplied by the service). Behaviour-preserving — same batch retry,
5-attempt limit, 500ms success grace, and haveAnyRetryableSubscriptionsErrored
semantics. No test changes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…efactor-graphql-service

# Conflicts:
#	packages/javascript-api/src/lib/services/graphql/graphql.service.ts
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