Skip to content

feat: neo4j EXTENDS/IMPLEMENTS inheritance edges#41

Open
rahlk wants to merge 1 commit into
chore/issue-32-formalize-reaching-defsfrom
feat/issue-33-neo4j-inheritance-edges
Open

feat: neo4j EXTENDS/IMPLEMENTS inheritance edges#41
rahlk wants to merge 1 commit into
chore/issue-32-formalize-reaching-defsfrom
feat/issue-33-neo4j-inheritance-edges

Conversation

@rahlk

@rahlk rahlk commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Closes #33. Part of epic #26 (contract-correctness cluster).

Stacked PR 7 of 7 — base: chore/issue-32-formalize-reaching-defs; review this PR's diff in isolation. Merge the stack bottom-up into feat/issue-2-program-graphs.

Verified: full suite 99 pass / 0 fail, typecheck clean, schema.neo4j.json in lockstep. Reviewed (task-scoped + final whole-branch review: READY TO MERGE).

…hips

Resolves each type's heritage signatures (base_classes/implements_types)
through idBySig to can:// ids in the v2 emitter, dropping unresolved
external/library supertypes rather than nulling them. Exposes the result
as extends_ids/implements_ids on the V2 type node (JSON props unchanged)
and projects them as EXTENDS/IMPLEMENTS relationships in Neo4j via the
previously-dead RowBuilder.edgeToSymbol deferred gate, which was also
re-pointed at the correct CanNode/id addressing (it had been hardcoded to
a Symbol/signature pair no node in the v2 schema actually carries).

Adds a first-party class hierarchy fixture to dataflow-app and extends
both the schema conformance test and the issue #27 Neo4j<->JSON parity
gate (the latter now also has an exhaustive total-edge accounting test).
@rahlk rahlk force-pushed the feat/issue-33-neo4j-inheritance-edges branch from f9502b2 to bdd1aed Compare July 7, 2026 10:38
@rahlk rahlk force-pushed the chore/issue-32-formalize-reaching-defs branch from 2a32e42 to f0d78ce Compare July 7, 2026 10:38
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