Skip to content

fix: carry analyzer name+version on the neo4j :Application node#48

Open
rahlk wants to merge 2 commits into
feat/issue-33-neo4j-inheritance-edgesfrom
fix/issue-43-neo4j-application-version
Open

fix: carry analyzer name+version on the neo4j :Application node#48
rahlk wants to merge 2 commits into
feat/issue-33-neo4j-inheritance-edgesfrom
fix/issue-43-neo4j-application-version

Conversation

@rahlk

@rahlk rahlk commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Closes #43. Epic #26 follow-up.

Stacked on feat/issue-33-neo4j-inheritance-edges (on top of the compliance cluster). Review this PR's diff in isolation; merge the follow-up stack bottom-up after the cluster.

Verified: 104 tests / 0 fail, typecheck clean, schema.neo4j.json lockstep; task-scoped review + final whole-branch review (READY TO MERGE).

rahlk added 2 commits July 7, 2026 07:12
The JSON envelope advertises analyzer{name,version} (#29), but the
Neo4j :Application node had neither — so the two co-primary
projections diverged on analyzer identity. project() now sources
name/version from the same V2Application.analyzer the envelope uses
(populated from ANALYZER_VERSION in src/utils/version.ts), declared
in the schema catalog and regenerated into schema.neo4j.json.
…sion

Bare name/version on :Application collided with project()'s _appName param
and every other CanNode's bare `name`. Namespace analyzer identity the same
way the JSON envelope does (analyzer{name,version}), unambiguous from the
node's own identity fields.
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