fix(docs): remove suggestion of libavoid for edge routing #333
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Thanks for this! You're right it's not great if we send people down wild goose hunts: I found this but doesn't seem fit for prime time yet https://github.com/Aksem/libavoid-js Thanks again :) |
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.
The Layouting docs currently suggest that elkjs supports libavoid as an edge routing solution. While ELK (the Java version with all the docs) supports libavoid, it's not supported by elkjs (as of yet); see kieler/elkjs#210.
This PR removes the link to elkjs and libavoid in the edge routing section since it can easily be confusing and take some time to figure out why libavoid isn't working with elkjs.