Fix Sync Streams json_each object and scalar evaluation#647
Open
sravan27 wants to merge 1 commit into
Open
Conversation
🦋 Changeset detectedLatest commit: 7a6bae6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes a Sync Streams JavaScript evaluator divergence from SQLite around
json_each().SQLite's
json_each()emits rows for JSON arrays, JSON objects, and scalar JSON values:The current JavaScript table-valued-function evaluator only accepts arrays, throws for objects, and cannot expose the
keycolumn. That means valid Sync Streams rules using object-shaped request/JWT/connection JSON can fail or diverge when evaluated by the JavaScript engine.This PR:
key = null.keyandvaluecolumns from the JavaScript evaluator.json_each()evaluation.@powersync/service-sync-rules.Verification:
Note: the local
node:sqliteside of this engine test still hits the same local Node binding issue seen on earlier Sync Streams PR verification (column index out of rangewhile binding table-valued JSON inputs), so I scoped the runnable local test command to the JavaScript evaluator path this patch changes.