Skip to content

content-node: read ids through graphCoreId in four more handlers - #518

Merged
adamjohnwright merged 1 commit into
mainfrom
refactor/graph-core-id
Oct 17, 2026
Merged

adamjohnwright merged 1 commit into
mainfrom
refactor/graph-core-id

Conversation

@adamjohnwright

Copy link
Copy Markdown
Contributor

Belongs to spec 006 (no task of its own; it tidies the endpoints T019–T026 ported).

Four handlers each carried their own copy of graph-core's id reading, REACT_ lookup included:

  • /participants/{id}
  • /participants/{id}/referenceEntities
  • /detail/{id}/locationsInPWB
  • /instance/{id}/referrers

They now share graphCoreId, which #514 introduced. diagramResult and orthologyOf read ids through inDepthId, a different rule, and keep their own lookup.

No change in behaviour: byte-identical to Java over 20 requests across the four handlers, with stable, dbId, REACT_ (found and not) and unreadable ids.

Review: an adversarial review compared each removed block with graphCoreId and found them word for word the same. It checked what each handler returns for an id it can't read, the {id} params shape, byDbId, and that no use of the removed where is left. The one comment lost with the old blocks (findNewStId) is now in graphCoreId's doc comment.

🤖 Generated with Claude Code

/participants/{id}, /participants/{id}/referenceEntities,
/detail/{id}/locationsInPWB and /instance/{id}/referrers each carried
their own copy of graph-core's id reading, REACT_ lookup included; they
now share graphCoreId. No change in behaviour: byte-identical to Java
over 20 requests across the four, with stable, dbId, REACT_ (found and
not) and unreadable ids. diagramResult and orthologyOf read ids through
inDepthId, a different rule, and keep their own lookup.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@adamjohnwright
adamjohnwright merged commit 80fdfbd into main Oct 17, 2026
7 checks passed
@adamjohnwright
adamjohnwright deleted the refactor/graph-core-id branch October 17, 2026 20:56
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