Skip to content

materialize: remove deprecated constraints from materialize protocol#3104

Open
mdibaiee wants to merge 2 commits into
masterfrom
mahdi/remove-deprecated-constraints
Open

materialize: remove deprecated constraints from materialize protocol#3104
mdibaiee wants to merge 2 commits into
masterfrom
mahdi/remove-deprecated-constraints

Conversation

@mdibaiee

@mdibaiee mdibaiee commented Jul 2, 2026

Copy link
Copy Markdown
Member

Description:

Workflow steps:

(How does one use this feature, and how has it changed)

Documentation links affected:

(list any documentation links that you created, or existing ones that you've identified as needing updates, along with a brief description)

Notes for reviewers:

(anything that might help someone review this PR)

mdibaiee and others added 2 commits July 2, 2026 14:22
The `test_field_selection` wasm test and the FIELD_SELECTION.md example
still supplied connector constraints via the removed `constraints` map.
After removing that field, the map is silently dropped on deserialization,
so every field became ConnectorOmits and the assertion failed. Switch the
fixture and doc to the equivalent `projectionConstraints` list form.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant