genshacl
: fix the propagation of types
to SHACL sh:datatype
and sh:nodeKind
#2102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the previous state, the edited code was never reached. With this change, a linkml or custom type as slot range will propagate to the property's
sh:datatype
in SHACL. In addition, ash:nodekind
ofsh:Literal
is added for such properties (based on my interpretation of this comment)This PR is intended to close #1299. It does pretty much the same as #1300, but that PR has been stagnant for over a year and is based on old state of
main
. So I though a fresh PR might be useful to get the fix merged. Happy to close again if the preference would be to rather update the existing PR.TODO: