Recursive node creation #118
Merged
Conversation
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
Mec-iS
requested changes
Jul 3, 2019
Redis, Redis Graph and Hydra Python Core with the proper readme observation and so on
gustavodemorais
force-pushed
the
develop
branch
2 times, most recently
from
1d85b83 to
45f1b4d
Compare
Failling before beucase it would try to fetch hydrus for internal resouces if doc has a property that has an URL
gustavodemorais
commented
Jul 5, 2019
vddesai1871
reviewed
Jul 6, 2019
Mec-iS
approved these changes
Jul 7, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #
#113
Checklist
Description
Now the agent create nodes and links to all URIs embedded in a resource property when finding one
Discussion
One thing that popped in my mind and I couldn't find an answer is about the name of the edge. I.e:
StateCollection -> has_State -> State1
Drone123123 -> has_State -> State1
Should we define a different naming for edges between collections-members and members-members?