Skip to main content

vendure 7.6.1 copy "vendure: ^7.6.1" to clipboard
vendure: ^7.6.1 copied to clipboard

Typed Dart and Flutter SDK for Vendure GraphQL APIs - channel-aware catalog, cart, checkout, payment, and admin domain clients.

7.6.1 - 2026-11-20 #

7.6.1: pub.dev score improvements across the fleet — added a pana-recognized example/README.md to 12 packages (zuraffa_observability, session, storage, graphql, minio, tui, ffi, vendure, flutter, inappwebview, ocr, purchase); cleared all analyzer infos in zuraffa and zuraffa_flutter (deprecated flutter/material.dart -> material_ui, withOpacity -> withValues) for 50/50 static analysis.

7.6.0 - 2026-11-19 #

Fleet release 7.6.0: zuraffa_observability moves its OTel base to dartastic_opentelemetry with a sealed test-capture seam + facade re-exports (issue #4); zuraffa_vendure + zuraffa_graphql adopt graphql_plus ^5.3.0; fleet-wide zorphy/zorphy_annotation raised to ^2.5.1 with all entities regenerated from scratch.

7.5.0 - 2026-11-15 #

Release 7.5.0: Signal-backed view-state migration template with SignalScope ownership (#2076); signal listener/subscription cleanup on eager-delivery throw (#2081, #2083); UseCase/StreamUseCase catch-all SEVERE logs now carry the cause (#2077, #2079); dependencies upgraded and pinned to latest resolvable.

7.4.2 - 2026-11-13 #

  • Mono-version fleet alignment to 7.4.2; internal dependencies refreshed; xml override 7.1.0.

7.4.1 - 2026-11-11 #

Fleet release 7.4.1: core adds zfa tunnel (Cloudflare-hosted MCP servers), MCP streamable-HTTP transport with usecase tools, blocking lifecycle hooks (#2032), typed tool param coercion (#2061); whole fleet mono-aligned to 7.4.1.

Unreleased #

Two transport regressions from the 7.x reimplementation, both reported live on zik_zak (websocket churn + unhandled Bad state: Future already completed):

  • Subscriptions speak graphql-transport-ws again. The reimplementation dropped the source SDK's subProtocol: GraphQLProtocol.graphqlTransportWs on the subscription WebSocketLink, silently falling back to the legacy graphqlWs protocol. Vendure servers close the socket right after connection_init, and with autoReconnect that becomes the endless Connected to websocket → Initialising connection → Disconnected from websocket loop (reconnect every 5s, forever). Restored from vendure-flutter-sdk 3.0.1 _getSubscriptionClient.
  • The timeout parameter is wired into the client. VendureContext.timeout was dead code: the main GraphQLClient was built without queryRequestTimeout, so graphql's silent 5s default applied — exactly what consumers like zik_zak disable on purpose (zik_zak issue 265: the budget is enforced per call instead). The default's Stream.timeout fires a synthetic TimeoutException while the late real response still completes the query manager's unguarded onData completer a second time — the unhandled Bad state: Future already completed crash through HttpLink.request + the AuthLink chain. queryRequestTimeout: context.timeout restores the source SDK's queryRequestTimeout contract (timeout: null = no transport-level timeout).
  • Regression suite: T1–T4 in test/graphql_datasource_suite_test.dart pin the client request timeout (context-carried, null = disabled) and the subscription wire configuration (protocol, endpoint scheme/languageCode swap).
  • The timeout wiring no longer arms graphql's Stream.timeout. Passing context.timeout into GraphQLClient.queryRequestTimeout (the 7.3.8 regression, issue #8) armed a Stream.timeout on every Shop API call: when the stream went quiet past the budget, the request failed as a synthetic TimeoutException (No stream event) and the late real response then double-completed the query manager's unguarded completer — the unhandled Bad state: Future already completed crash in the root zone (graphql 5.2.4, query_manager.dart). The client now pins queryRequestTimeout: null (explicit — omitting restores the silent 5 s default), and the datasource enforces VendureContext.timeout in _executeRaw / mutateWithHeaders via cancellable Future.timeout, translating expiry to VendureDataSourceException. Regression suite: T1 re-pinned, T5–T7 in test/graphql_datasource_suite_test.dart (a quiet stream surfaces a clean exception with zero unhandled async errors; the late response lands silently).
  • Transport moved to the hardened graphql_plus fork. The unhandled Bad state: Future already completed had a root cause in the dependency, not only in vendure's wiring: stock graphql 5.2.4's QueryManager passes completer.complete straight to Stream.listen, so once Stream.timeout has settled the completer the late response completes it again from inside the stream callback — where fetchQuery's try/catch cannot reach it. The dependency is now graphql_plus: ^5.2.5 (arrrrny's fork of 5.2.4), which guards onData/onError with isCompleted, cancels the subscription once the completer settles, and surfaces an empty response stream as StateError('No element') instead of hanging. The fork renamed the library file, so package:vendure/graphql.dart is the stable import for the transport types on vendure's public surface. Regression: T8 in test/graphql_datasource_suite_test.dart (red on 5.2.4, green on the fork).
  • BREAKING (transport imports): a consumer that imported package:graphql/client.dart to name a client type (to build an injected GraphQLClient, say) must import package:vendure/graphql.dart instead — re-exported by package:vendure/vendure.dart, so the package's documented entrypoint is enough. graphql is no longer a dependency of vendure, and a same-named class from a consumer's own graphql resolution is a different type from the one vendure's transport actually speaks.
  • Barrel reachability is now pinned: test/barrel_transport_surface_test.dart imports only package:vendure/vendure.dart and names GraphQLClient, so dropping export 'graphql.dart'; from the barrel fails the suite at compile time instead of only in a consumer's build (arrrrny/zuraffa_vendure#15).
  • BREAKING (datasource port): CustomOperations' expectedDataType no longer defaults to 'data'. That default was a guaranteed-throw: the GraphQL client unwraps the top-level data envelope before the SDK sees a QueryResult, so _handleErrors looked for a data key INSIDE the operation's own field map, found none, and threw No data returned for expected type: data — on responses the backend had accepted (arrrrny/zuraffa_vendure#17; live as zik_zak#877 and zik_zak#897, where four listing posts false-failed since 2026-11-09). The default is now null: the adapter returns the document's single root field (__typename excluded — gql() injects it into every selection set), or the whole envelope for a multi-field document. A root field the server answered with null (a guest session's activeOrder) is that answer, not a failure; only an absent name still throws, and it reports the keys the response DID return (… (envelope keys: [postListing])) instead of a bare name. queryListPaginated / mutateListPaginated now fail loudly when a multi-field envelope reaches them with neither items nor totalItems, where they used to report a real page as items: [], totalItems: 0. Widening the port is a source break for anyone who implements VendureDataSource outside this package: query, mutate, queryList, mutateWithHeaders and subscribe take required String? expectedDataType (a String-typed override no longer compiles — invalid_override), VendureRequestRecord.expectedDataType is nullable, and InMemoryVendureDataSource.script is Map<String?, dynamic>. Those implementers must widen their parameter types. The widened public port takes a MINOR bump: 7.5.0 is released, so this lands as 7.6.0. Regression: D1–D10 in test/custom_operations_default_expected_data_type_suite_test.dart.

7.3.6 - 2026-11-02 #

  • Fix: CustomOperations.queryListPaginated / mutateListPaginated restore the source SDK's envelope normalization — __typename → runtimeType before fromJson (with the caller's convertEnums honored on output, which was previously dead on this path). gql() injects __typename into every selection set and the raw escape hatch returns the payload as-is, so polymorphic entity decoders (zorphy explicitSubTypes fromJson — e.g. zik_zak's Listing.fromJson) threw UnsupportedError: The __typename 'ChannelListing' is not supported… on every paginated row. Regression suite: test/custom_operations_paginated_suite_test.dart (zuraffa_vendure#2, PR#3).
  • Mono-version fleet alignment to 7.3.6; internal dependencies refreshed; xml override 7.1.0.

7.3.5 #

  • Fix: Vendure._finalizeInitialization connection-check query now passes fromJson: null so the scalar __typename string return doesn't fail the Map<String, dynamic> expectation.

7.3.4 #

  • Fix: CurrentUserChannel.code is now nullable. Real Vendure backend authenticate / firebaseAuth mutations select channels { id token permissions } without code, which previously caused CheckedFromJsonException during JSON decoding.

7.3.3 #

Hotfix (consumer-reported via the fleet verification round — zik_zak's vendure-client init scenarios):

  • mutateWithHeaders tolerates an absent body — the auth seam's contract is headers-only (the session token rides the vendure-auth-token response header). A mutation whose expectedDataType key is absent in the response (e.g. a firebase token-exchange server answering with only __typename) now resolves to null data instead of throwing No data returned for expected type: authenticate, matching vendure-flutter-sdk 3.0.1's AuthBaseOperations.extractResponseHeaders. VendureResponse.data is T?.
  • Regression locks A2 (in-memory, headers-only firebase exchange) and G10 (graphql adapter, __typename-only response).

7.3.2 #

The Zuraffa reimplementation of the Vendure Flutter SDK, shipped as the same vendure package name.

  • Facade (Vendure): five init variants + forTesting, the runtime setters (auth token, languageCode, channelToken, apiKey), refreshToken, destroy, GetIt registration (registerVendureDependencies / registerVendureTestDependencies), and the connection-check ping.
  • Six operation groups on the facade: order, auth, customer, catalog, system, custom (raw query/mutate/queryList/mutateList, paginated variants, response-header extraction).
  • Datasources: the VendureDataSource port (one error path — VendureDataSourceException), GraphQLVendureDataSource (link chain: HttpLink → apiKey → vendure-token → App Check → Bearer; noCache policies; __typename→runtimeType normalization; transient-network retry; WebSocket subscriptions with the Vendure initialPayload), and the pure-Dart InMemoryVendureDataSource (scripted payloads, request recording, response-header scripting).
  • Entities: the schema's 179 entities as zorphy types (11 enums + SearchResultPrice included), and the 18 mutation unions as hand-written sealed classes dispatching on the wire runtimeType key.
  • Auth: DataAuthRepository with the AuthErrorClassifier credential vocabulary; the session token is captured from the vendure-auth-token response header via mutateWithHeaders.
  • Token lifecycle: TokenManager + TokenLocalDataSource seam with the fetch-refresh closure wired by the facade.

Port fidelity notes (from vendure-flutter-sdk 3.0.1) #

  • queryList requires the extracted payload to be a bare list; scalar lists (e.g. nextOrderStates) decode without a fromJson.
  • custom.query/mutate accept an optional fromJson; omitted, the extracted payload returns raw (scalar/Map/List).
  • Response normalization (__typename → runtimeType, enum conversion off) runs before the typed decode on both adapters, so the sealed unions dispatch exactly like the old SDK's remote path.
  • The old SDK's CustomOperations built a second datasource; this port wires the facade's single datasource through, so custom operations share the context, the error path, and the retry policy.

Tests #

24 behavioral tests, pure Dart, no network: the port contract and one error path (D1–D6), the GraphQL adapter's envelope/dot-path/ErrorResult handling, context assembly, and the union wire-dispatch normalization (G1–G9), and the facade lifecycle plus per-group request-shape fidelity (F1–F4, O1–O3, A1, C1) through the scripted in-memory datasource.

7
likes
150
points
2.31k
downloads

Documentation

API reference

Publisher

verified publisherzuraffa.com

Weekly Downloads

Typed Dart and Flutter SDK for Vendure GraphQL APIs - channel-aware catalog, cart, checkout, payment, and admin domain clients.

Homepage
Repository (GitHub)
View/report issues

Topics

#vendure #commerce #graphql #flutter

License

MIT (license)

Dependencies

get_it, graphql_plus, http, json_annotation, meta, zorphy_annotation, zuraffa

More

Packages that depend on vendure