You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Handle Impossible to generate slot usage entry complaints about changes in the range metadata slot #406
This issue can be closed. Both tasks are done, on linkml-conversion.
The wording changed, as in #407. The complaint is no longer Impossible to generate slot usage entry. After dandi/pydantic2linkml#71 allowed partial slot_usage entry generation, both instances read Cannot express in a slot_usage entry a value for the `range` .
Fix. Both ranges are now specified explicitly through dandischema/models_merge.yaml, and the notes they made obsolete are stripped during sanitization:
6c7f0e7: specify the range of Dandiset.wasGeneratedBy as Project
a786022: specify the range of BareAsset.wasGeneratedBy as Any, alongside its existing any_of
75341f3: allow note removal to be scoped to locations in the document, so the removal targets only these two notes
5b50b3c: drop the obsolete range notes on the two wasGeneratedBy slot usages
Second task, the LinkML behavior check.tests/linkml_behavior/range_refinement/ pins both respecifications the fix depends on (narrowing a range to a subclass, and widening it to Any constrained by an any_of) against all three validators the pipeline uses: linkml-validate, gen-json-schema and gen-pydantic.
e259d12: make the topic directories packages so sibling topics can coexist
These run in CI under the existing LinkML behavior tests workflow (hatch run linkml-behavior-test:test).
Result, visible on linkml-auto-converted at c17f4b5: both notes entries are gone, replaced by range: Project and range: Any. No such complaint about the range meta slot remains in the generated models.yaml.
Activity
pydantic2linkml: Impossible to generate slot usage entry for the#389candleindark commentedon Aug 3, 2026
This issue can be closed. Both tasks are done, on
linkml-conversion.The wording changed, as in #407. The complaint is no longer
Impossible to generate slot usage entry. After dandi/pydantic2linkml#71 allowed partialslot_usageentry generation, both instances readCannot express in a slot_usage entry a value for the `range`.Fix. Both ranges are now specified explicitly through
dandischema/models_merge.yaml, and the notes they made obsolete are stripped during sanitization:Dandiset.wasGeneratedByasProjectBareAsset.wasGeneratedByasAny, alongside its existingany_ofnotesrangenotes on the twowasGeneratedByslot usagesSecond task, the LinkML behavior check.
tests/linkml_behavior/range_refinement/pins both respecifications the fix depends on (narrowing a range to a subclass, and widening it toAnyconstrained by anany_of) against all three validators the pipeline uses:linkml-validate,gen-json-schemaandgen-pydantic.range_refinementtopicThese run in CI under the existing
LinkML behavior testsworkflow (hatch run linkml-behavior-test:test).Result, visible on
linkml-auto-convertedat c17f4b5: bothnotesentries are gone, replaced byrange: Projectandrange: Any. No such complaint about therangemeta slot remains in the generatedmodels.yaml.candleindark commentedon Aug 3, 2026
@yarikoptic Please take a look. Let's close this if you are OK.