-
Notifications
You must be signed in to change notification settings - Fork 49
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
Refactor to use display entities #698
Merged
Merged
Changes from 1 commit
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
a536b48
Fix edge type display label
kmcginnes 56b0f42
Move icon defaults to constants
kmcginnes ea7aeca
Add useQueryEngine hook
kmcginnes 6c83f2a
Use toSorted() instead of sort()
kmcginnes d80bd80
Use display vertex and edge
kmcginnes a66e7c6
Update changelog
kmcginnes 21f1d9a
Remove commented out code
kmcginnes fc34e7b
Fix name in displayAttribute
kmcginnes 0698768
Use vertexTypes
kmcginnes 0c94baf
Use constant for “types”
kmcginnes 96dc448
Use set for type lists
kmcginnes e4f3768
Pull up displayNodes lookup
kmcginnes 50d830e
Move display name logic to displayEdge
kmcginnes 66916be
Consolidate attribute styles & add edge properties
kmcginnes c8fbfd9
Remove unused functions
kmcginnes 5533424
Improve the imports
kmcginnes d4092ff
Only map the selected vertices & edges
kmcginnes d7cce57
Update default display label to undefined
kmcginnes 74b9ada
Update changelog
kmcginnes 2e04821
Fix random test failures
kmcginnes 465ab32
Add tests for displayAttribute
kmcginnes b541601
Revert to nullable displayId
kmcginnes 7a2c8ee
Revert "Revert to nullable displayId"
kmcginnes 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 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
This file contains 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
This file contains 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
This file contains 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
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.
Curious why this check is preferred to the original check for
displayId
? Is there still value in setting thedisplayId
on theEdgeDetail
for SPARQL if it's not shown?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 honestly don't remember why I made that change. If I had to guess it was to make sure no properties were optional on the model. But that's not a good enough reason.
I reverted the change.
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.
Actually, I take it all back. After reverting the change and seeing some errors I now remember why. It is about optionality, but specifically around the logic to get the "display name" value. Since
displayId
is an option on non-sparql databases if it was optional it would require display name to be optional, which I do not want.