Any attempt to fixing it via a local patch has proven to not work (so far).
I am starting to suspect that the issue may be in the model specification. The datetime range is (would be) declared in a mixin. Maybe a (re)declaration in the schema element class would cause the linkml tooling to pick up the correct info in all scenarios.
Some information is reported to linkml at https://github.com/linkml/linkml/issues/1806
Any attempt to fixing it via a local patch has proven to not work (so far).
I am starting to suspect that the issue may be in the model specification. The
datetime
range is (would be) declared in a mixin. Maybe a (re)declaration in the schema element class would cause the linkml tooling to pick up the correct info in all scenarios.