Skip to content

Add concept_class and datatype to cascade hierarchy view#823

Open
paynejd wants to merge 1 commit intomasterfrom
cascade-hierarchy-concept-class
Open

Add concept_class and datatype to cascade hierarchy view#823
paynejd wants to merge 1 commit intomasterfrom
cascade-hierarchy-concept-class

Conversation

@paynejd
Copy link
Member

@paynejd paynejd commented Mar 21, 2026

Summary

  • Add concept_class and datatype to ConceptMinimalSerializerRecursive so the cascade hierarchy view includes these fields
  • Update integration tests to expect the new fields
  • Purely additive change — no existing fields modified, nested entries structure preserved

Motivation

Clients (like ocl-cli) need concept class/datatype when rendering cascade trees. Currently the hierarchy view omits these, forcing a second flat+verbose API call and client-side merge to enrich the tree nodes. This doubles the API cost for a common use case.

Test plan

  • Existing cascade integration tests pass with updated field assertions
  • Hierarchy view response now includes concept_class and datatype per concept node
  • Flat view behavior unchanged

🤖 Generated with Claude Code

The hierarchy view's ConceptMinimalSerializerRecursive only returned
minimal fields (id, display_name, retired, etc.), forcing clients to
make a second flat+verbose API call to get concept_class and datatype.

Add these two fields to the serializer. This is purely additive —
no existing fields change, the nested entries structure is preserved.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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