-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
3952 - lexical ids #4785
3952 - lexical ids #4785
Conversation
Co-authored-by: Alois Klink <[email protected]>
✅ Deploy Preview for mermaid-js ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #4785 +/- ##
===========================================
- Coverage 80.50% 74.57% -5.94%
===========================================
Files 148 146 -2
Lines 13024 14529 +1505
Branches 612 613 +1
===========================================
+ Hits 10485 10835 +350
- Misses 2405 3569 +1164
+ Partials 134 125 -9
Flags with carried forward coverage won't be shown. Click here to find out more.
|
id: 'id' + cnt, | ||
id: 'id_' + edge.id1 + '_' + edge.id2, |
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.
Is this the only relevant part for lexical IDs?
If so, can you reset your branch to develop and only have this in the PR?
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 think the cnt should also be in the ID.
Otherwise, id of [a, b_c] and [a_b, c] will both be id_a_b_c, leading to a conflict.
will resubmit |
📑 Summary
Changed ids of edge paths for relationships to use class names for easier identification in code
This includes the changes in #4582 and #4534, so those should be merged first
Resolves #3952