-
Notifications
You must be signed in to change notification settings - Fork 7
Change ld_list according to #439 #445
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
Merged
SKernchen
merged 26 commits into
refactor/385-test-ld_list
from
refactor/439-restrict-ld_list
Dec 19, 2025
Merged
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
da136c3
changed ld_list according to issue #439
03ebd32
implemented tests for problem 2 of the issue and more tests
d1eb612
added a few missing conversions and formatted the file a little bit d…
d28dc10
removed one conversion, added one and changed _to_python to fix conve…
fb5aa64
fixed formatting errors
5248853
fixed ld_container tests, a type conversion and equals of ld_list
e2c1bba
added detailed comparison for ld_list, ld_dict and json_values and ad…
aeb88fb
added support for graph and set again and improved expansion of json-ld
007e3a3
removed unnecessary lambda
3c9ea61
fixed set and from_list and added del
66e03df
updated tests of ld_container and fixed found bugs
c4aea65
pacified flake8
7d30b16
improved ld_list.__contains__ and added tests for it
f8d259f
added one TODO item to ld_list
2b98627
began adding doc strings, type hints and comments for ld_container
1958518
improved _to_expanded_json
4acf8de
added doc-strings and comments and pacified flake8
b751130
began commenting and adding doc-strings to ld_list
3c243f2
fixed bug in _to_expanded_json
e0f0fc9
added a few test cases to delete of ld_list
1b5656e
added more comments to ld_list
071630c
added more doc strings
d4b34b4
corrected type hints
f0f1818
documented the rest of the methods in ld_container
bcc233d
implemented list comparison and added tests for it
287d37a
added tests and fixed small bug and fixed typos
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This rule is to generic IMHO, as it will try to compact all strings that are encountered, even those that are explicitly not meant as representing an IRI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But shouldn't all other string should be known to be a value of some sort i.e. formed like
{"@value": _}and therefor filtered by is_json_value because we get valid JSON-LD?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see you have answers... but I'm totally not sure whether this is really true.
Apart from this, except for
@typevalues, all expansible values should be wrapped in@idnodes... maybe this is a good point to check whether this assumption is correct. The other question is, which kind of expansion is required (i.e., vocab=True or not... see discussion about prefix, namespace, IRIs from the past)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... anyways, there should most proably be a documentation for the conversion rules and the order they are applied in (maybe directly generated from the code... ;) )