Rework schema data structure #64
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
108ef15 to
199470e
Compare
Before this change, the data was grouped by the type of edge and node. This is now restructured into nodes and edges with tags to carry the extra information. The view logic has been altered so that the data sent to the front-end is the same for now.
199470e to
9519964
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We used to generate the schema with each type of edge and node in a different list.
This instead groups everything into edges or nodes, and marks those differences with "tags" such as
"abstract"etc.Some work is done in the view to convert back into the old format so that the work on the front-end can be handled separately.