zonai_client 0.2.2

Typed Dart and Flutter client for a Zonai backend: auth, CRUD, file uploads, and live SQLite query streams over HTTP.

0.2.2

• The barrel now exports the query vocabulary, so a consumer can name the types the generated typed client takes and returns. zonai gen client emits code whose signatures are Where, Update, OrderByTerm and friends; before this, that code compiled only if the app also depended on zonai_schema directly and imported it by hand, which defeats the point of a generated client. Added: Where, Update, UpdateValue, ColumnUpdate, ObjectUpdate, OrderByTerm, SortDirection, the comparison and set clauses (Eq, Gt, Gte, Lt, Lte, In, NotIn, And, Or, Literal), the string clauses (Contains, NotContains, StartsWith, EndsWith), and the mutation values (Add, AddAll, Remove, RemoveAll, Increment, Decrement). Also newly exported are the data sources a typed client hangs off — Db, DbListen, AdminAuth, Emails, Photos. Purely additive; nothing was removed or renamed.
• Null and NotNull are deliberately not exported, and this is the one place the addition is not mechanical. A library that imports them shadows dart:core's Null, because Dart resolves an explicit import ahead of the implicit dart:core one — so every Null written in that library would mean the where-clause class instead. Build those clauses with Where.isNull / Where.isNotNull (new in zonai_schema), which redirect to them. If you already import package:zonai_schema/payloads.dart directly and rely on Null, nothing changes for you.
• The zonai_schema lower bound moves to >=0.4.1 (was >=0.1.0). It is load-bearing for the first time: Where.isNull / Where.isNotNull are the documented way to build the two clauses this barrel withholds, and they do not exist below 0.4.1. Against 0.4.0 this package would export a query vocabulary with no way to express IS NULL, and zonai gen client output — whose runtime calls Where.isNull — would not compile.

0.2.1

• Widen the zonai_schema constraint to >=0.1.0 <0.5.0 so consumers can move to zonai_schema 0.4.0. The published 0.2.0 declares <0.4.0, which excludes it — anyone using this client alongside zonai_schema is pinned below 0.4.0 regardless of what they ask for, and 0.4.0 is the release carrying push notifications and the tightened auth defaults that Zonai CLI v0.8.0 requires. Nothing here references what changed in 0.4.0 (push vocabulary and rate-limit defaults, both server-side), so this spans the minors rather than pinning to the newest.
• OAuth reaches the client. Auth gains providers({table}), startUrl({...}), complete({...}) and signInWithIdToken({...}), covering both the redirect flow and the native one. Underneath, AuthDataSource gains startOAuth, oauth, oauthProviders, oauthCallbackFormPost and acceptAdminInvite, and a new AdminDataSource (members, invite, revokeInvite, removeMember) is reachable as client.admin. Additive throughout; the package's exported entrypoint surface is unchanged.
• The generated client gains MaintenanceDataSource — purgeLogs, purgeTable, cleanupPhotos and reclaimLogSpace, reachable as client.maintenance — and DashboardDataSource.storage(), which back the dashboard's new Maintenance screen.
• EmailDataSource.send, RootDataSource.swaggerJson and RootDataSource.swaggerYaml now take an optional authorization argument, because the server no longer serves those unauthenticated. Additive for callers; if you implement or mock any of these interfaces yourself, you will need to add the parameter and the new members.

0.2.0

• Breaking: require revali_client ^3.0.0 (was ^2.1.0). This is breaking for you only if you pass your own interceptor to ZonaiClient(extraInterceptors: [...]), because HttpInterceptor.onRequest and onResponse now return FutureOr<HttpResponse?> instead of void. The migration is mechanical: change the return type and return null, which means "carry on". Returning a response instead is the new capability — from onRequest it answers the call without sending anything, and from onResponse it substitutes what arrived, which is what makes retries, caching and circuit breaking expressible at all. Callers who pass no interceptor of their own are unaffected; this package's own X-Auth interceptor already returned null throughout.
• Behaviour change, no API change: a throwing interceptor now fails the request instead of being swallowed. Previously an interceptor that threw let the request continue in whatever half-prepared state it was left in, so a failed auth interceptor put an unauthenticated request on the wire and surfaced as a puzzling 401 from the server rather than as an error where it actually broke. If you relied on that swallowing, catch inside your interceptor.
• The bundled revali_client also gains RevaliClient.timeout and an opt-in RetryPolicy, and ServerException now parses the server's error envelope (code, reason, details, isStructured) when one was sent. This client does not yet configure any of them; they are listed because they arrive in the dependency you now resolve.
• No change to this package's own public API, generated client, or zonai_schema constraint. The generated client is byte-identical under revali_client_gen 2.5.0.

0.1.3

• Widen the zonai_schema constraint to >=0.1.0 <0.4.0 so consumers can move to zonai_schema 0.3.0. The published 0.1.2 declares <0.3.0, which excludes it — anyone using this client alongside zonai_schema is pinned below 0.3.0 regardless of what they ask for, and 0.3.0 is the release carrying the scheduled-cron fix. Nothing here references what changed in 0.3.0 (a revali_core major and new cron IPC vocabulary, both server-side), so this spans the minors rather than pinning to the newest.

0.1.2

• Widen the zonai_schema constraint to >=0.1.0 <0.3.0 so consumers can move to zonai_schema 0.2.0. The published 0.1.1 declares ^0.1.0, which excludes it — anyone using this client alongside zonai_schema was pinned below 0.2.0 regardless of what they asked for. Nothing here references the API that changed in 0.2.0 (TableRateLimits.customPolicy, which is server-side), so this deliberately spans both minors rather than pinning to the new one.
• Add RootDataSource.logo(), backing the optional dashboard logo served from imagesPath. Additive for callers; if you implement or mock RootDataSource yourself, you will need to add the member.

0.1.1

• Fix: lib/gen/ (the generated Revali HTTP client) was excluded from the published package by the repo's root .gitignore, making 0.1.0 unimportable. The generated client is now tracked and shipped.

0.1.0

• Initial release.