Closed ratmice closed 6 months ago
Can we fold this into a single thirdparty.md
file? I don't think we need a page per tool, but I agree that linking to nimbleparse_lsp from the book is a good idea.
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.
Squashed (with a minor grammar fix).
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.md
appends a.html
extension breaking the URL. Between adding a subsection, or just embedding a list within thethirdparty.md
I went with a subsection, since it more closely mirrored how the current list of tools and libraries is listed.