What's changing: The Service adds a new compatibility option, fixed_booleans_in_json, that syncs boolean values nested inside JSON objects, arrays, and custom Postgres types as JSON true/false instead of the integers 0/1.
High priority — existing docs are now inaccurate or incomplete
None identified. This is purely additive; existing behavior is unchanged unless the option is enabled.
For reviewer consideration — worth documenting
Source PR: powersync-ja/powersync-service#800 — open, labeled "Product Visibility"
Filed automatically by Claude Code (claude-sonnet-5). A human must verify the scope, prepare the docs PR, and publish it only once this update has been released.
What's changing: The Service adds a new compatibility option,
fixed_booleans_in_json, that syncs boolean values nested inside JSON objects, arrays, and custom Postgres types as JSONtrue/falseinstead of the integers0/1.High priority — existing docs are now inaccurate or incomplete
None identified. This is purely additive; existing behavior is unchanged unless the option is enabled.
For reviewer consideration — worth documenting
fixed_booleans_in_json, which would sit alongside the existingcustom_postgres_typesandunstable_sqlite_expression_enginerows.Source PR: powersync-ja/powersync-service#800 — open, labeled "Product Visibility"
Filed automatically by Claude Code (
claude-sonnet-5). A human must verify the scope, prepare the docs PR, and publish it only once this update has been released.