-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
list() does not always return an iterator #61
Comments
Thank you for pointing this out. Line 138 in 479607f
null . Do you refer to something else?
@bergos do you remember why we went for @martinmaillard can https://github.com/zazuko/rdf-validate-shacl deal with this? |
Ah, I mistakenly added links to files instead of lines. I wanted to refer to this line. You're right in that the Let me know if the validate-shacl library is a better place for ticket and I'll make an issue there |
This is by design, IIRC to distinguish between an empty list |
thanks! I'll report this in the validate-shacl repo then |
The function description of
list()
says that it always returns an iterator. In reality, it does not:This causes issues in e.g. the shacl validator where a spread operator is applied to the
list()
result (see here)Depending on the structure of your data, this leads to obscure errors such as
listNode.list is not a function or its return value is not iterable
The text was updated successfully, but these errors were encountered: