feat: replace MeaningUnitAspect enum with open-ended str#206
feat: replace MeaningUnitAspect enum with open-ended str#206asteier2026 wants to merge 2 commits into
Conversation
Greptile SummaryThis PR removes the
Confidence Score: 5/5Safe to merge — the change is narrowly scoped, removes a closed enum that was causing record loss, and replaces it with a validated open-ended string. All three changed files are consistent: the enum is fully deleted, the public re-export list is updated, tests use plain string equivalents, and both No files require special attention. Important Files Changed
|
The enum was causing record loss when the model returned values like "goal" or "symptom" that weren't enumerated. Aspect is now an unvalidated str to accommodate open-ended LLM output. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: asteier2026 <asteier@nvidia.com>
…hema.aspect Empty strings are structurally valid but semantically meaningless; guard against them consistently with the other non-id string fields in these schemas. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: asteier2026 <asteier@nvidia.com>
1856714 to
212a478
Compare
Summary
MeaningUnitAspectenum fromEntityDispositionSchemaandschemas/__init__.pyMeaningUnitSchema.aspectfromMeaningUnitAspecttostrMotivation
The enum was causing record loss: the model returns open-ended aspect values like
"goal","symptom","diagnosis"that can't be exhaustively enumerated. Validation errors were silently dropping records.