greenflags 0.3.0

Dart/Flutter SDK for GreenFlags feature flags. Snapshot + cache reads, polling, geofence evaluation and offline persistence — evaluated at the edge.

Changelog

Format based on Keep a Changelog. Versioning: SemVer (while in 0.x, a MINOR release may include breaking changes; strict semver applies from 1.0.0 onward).

0.3.0 - 2026-07-18

Added

• Percentage rollout evaluation: flags may carry rollout: { percentage }; the SDK buckets the current user deterministically (FNV-1a 32-bit over UTF-8 bytes of "flagKey:userKey", mod 100 — see docs/rollout-hash-spec.md) and serves the value when bucket < percentage, or the off value (false/null) otherwise. Conformance locked by sdks/rollout-test-vectors.json.
• Multivariate flags: variants: [{ name, weight, value }] assigned by cumulative weight ranges over the same bucket, variants ordered by name in UTF-8 byte order. A bucket beyond the total weight serves the base value.
• user constructor parameter and setUser(String?) — stable user key for bucketing; clearing reverts to an in-memory anonymous id (deterministic within the client's lifetime; pass a stable user for cross-session stickiness).
• Rollout, FlagVariant, WeightedVariant types and rolloutBucket/assignVariant exported from the package root.

Changed

• Evaluation chain: geofence → variants → rollout (AND; a rule with missing input is skipped). All read paths and snapshotStream emissions remain evaluated.

0.2.0 - 2026-07-11

Added

• geoDistanceMeters(a, b) — exported from package:greenflags/greenflags.dart. Returns the great-circle distance in meters between two Coordinates, the same haversine calculation the SDK runs internally for geofence evaluation. Lets apps show the live distance to a geofence without reimplementing it. No behavior change to flag evaluation.

0.1.0 - 2026-07-10

Added

• Initial release, mirroring @greenflags/client 0.2.x semantics in pure Dart.
• GreenFlagsClient with refresh, getSnapshot, getAllFlags, getFlag (with defaultValue), isEnabled, snapshotStream, startPolling/stopPolling, setCoordinates, dispose.
• Client-side geofence evaluation (haversine): outside the radius a boolean flag evaluates to false, other types to null. Every read path goes through evaluation — the raw snapshot is never exposed.
• Offline persistence via the SnapshotStore interface: hydrate() restores the last snapshot on startup; refresh() writes through. Raw flags are persisted so geofences re-evaluate against the current location after restart.
• Typed GreenFlagsException with API error code, message and HTTP status (NETWORK_ERROR/PARSE_ERROR client-side).
• Auth via Authorization: Bearer header against GET /v1/flags.