Skip to content

fix(gfql): preserve CALL/YIELD scope through strict row bind (#1371 P3) - #1387

Merged
lmeyerov merged 2 commits into
masterfrom
issue-1371-p3-call-yield-scope
May 9, 2026
Merged

lmeyerov merged 2 commits into
masterfrom
issue-1371-p3-call-yield-scope

Conversation

@lmeyerov

@lmeyerov lmeyerov commented May 9, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • bind CALL clauses before row-sequence projection binding when query shape is row-only
  • preserve YIELD aliases in strict name-resolution scope for downstream RETURN projection
  • add strict binder regression coverage for CALL ... YIELD ... RETURN ... (direct + aliased)
  • remove stale baseline note that still treated CALL/YIELD scope as unresolved

Validation

  • python -m pytest -q graphistry/tests/compute/gfql/cypher/test_binder.py -k "call_yield_scope or strict_name_resolution"
  • python -m pytest -q graphistry/tests/compute/gfql/cypher/test_binder_strict_compile_baseline.py
  • uv run ruff check graphistry/compute/gfql/frontends/cypher/binder.py graphistry/tests/compute/gfql/cypher/test_binder.py graphistry/tests/compute/gfql/cypher/test_binder_strict_compile_baseline.py

Refs #1371 (P3).

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