-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sub Graph support #2
Comments
Currently being addressed in FR2-SubGraphsRevisit |
TomNCatz
added a commit
that referenced
this issue
Apr 27, 2021
TomNCatz
added a commit
that referenced
this issue
May 3, 2021
TomNCatz
added a commit
that referenced
this issue
May 5, 2021
TomNCatz
added a commit
that referenced
this issue
May 6, 2021
TomNCatz
added a commit
that referenced
this issue
May 6, 2021
TomNCatz
added a commit
that referenced
this issue
Jan 1, 2022
TomNCatz
added a commit
that referenced
this issue
Jan 1, 2022
TomNCatz
added a commit
that referenced
this issue
Jan 1, 2022
TomNCatz
added a commit
that referenced
this issue
Jan 1, 2022
TomNCatz
added a commit
that referenced
this issue
Jan 1, 2022
TomNCatz
added a commit
that referenced
this issue
Jan 1, 2022
TomNCatz
added a commit
that referenced
this issue
Jan 1, 2022
TomNCatz
added a commit
that referenced
this issue
Jan 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Lists and dictionaries of complex objects currently have to be represented by parent child relationships that can quickly get unwieldy. Instead there should be an option for these lists to exist as subgraphs that are nested in the main graph and can be drilled down to.
The text was updated successfully, but these errors were encountered: