Add a doc section for third party tools #451
Merged
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
|
Can we fold this into a single |
|
Sure, I went ahead and did that. It means we don't get a link directly in the table of contents, but it seems more maintainable to just link directly to each project anyways instead of relying on potentially dated generic summary. |
|
Thanks! Please squash. |
ratmice
force-pushed
the
third_party_tools
branch
from
550d751
to
b090927
Compare
|
Squashed (with a minor grammar fix). |
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.
It was recommended in #448 to add a link to the book about nimbleparse_lsp.
I'm not really certain it is a good idea to advertise it yet, as it has fallen behind by a few releases and overall is still fairly
prototype quality.
Despite that, this adds "third party" section in chapter 6 of "individual libraries and tools".
I had hoped to just link directly to the repository, relying on the external readme.
Unfortunately trying to link to a
[lsp](https://)withinSUMMARY.mdappends a.htmlextension breaking the URL.Between adding a subsection, or just embedding a list within the
thirdparty.mdI went with a subsection,since it more closely mirrored how the current list of tools and libraries is listed.