Skip to content

fix(errors): align public parse and execution error taxonomy #353

Description

@DecisionNerd

Problem

The fail-closed public API BDD cutover in #347 exposed six documented error-class mismatches. Undefined variables, invalid aggregate placement, undirected CREATE relationships, duplicate aliases, type mismatches, and unbound parameters do not consistently surface as the documented ParseError or ExecutionError classes.

Acceptance criteria

  • Each documented invalid query returns the exact public error class and stable code.
  • Parse failures include the documented source span.
  • Rust, Python, and Node classify the same failure identically.
  • Mutation coverage rejects the wrong exception class.

Related to #347. These scenarios remain explicitly excluded from release-tested BDD evidence until this issue closes.

Activity

  1. coderabbitai commented on Aug 3, 2026

    @coderabbitai
    🔗 Related PRs

    #297 - docs(release): require one shared product version [merged]
    #351 - fix(bindings): repair Node bulk API contract [open]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions