-
Notifications
You must be signed in to change notification settings - Fork 63
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
feat: more languages supported #79
Comments
Alright. At the time of writing, we've got JavaDoc, HTML, and Bash supported, as well as |
If you could add |
Adding |
Hey, markdown support seems pretty advanced. 👍 Either way, I am thrilled about the project and being able to use a solid spell-checker LSP 🥳 : PS: Are you planning on adding a sponsoring option? |
Coming back to this issue after a solid period of stagnation, to give an update. #332 has added Haskell support, #354 is adding Vimscript, and #353 is adding I plan on adding PHP and potentially PowerShell later today.
We've got an open PR for Typst support: #302. I do not personally have time in the near future to add similar levels of polish to a new language as the Markdown parser. That said, we are entirely open to PRs on the topic, and I can answer any questions you may have. I'm not sure how complex djot is, but it may be as simple as importing the right Treesitter parser.
That's great to hear! I aim to please.
|
I'd like to expand the number of languages supported for comment checking. There are a number of additional considerations for structured comments (like JavaDoc), but some should be pretty straightforward.
Running list:
gitcommit
)In addition to adding language parsers to the tree-sitter code, we would also need to open pull requests for
nvim-lspconfig
,mason
and fixharper-ls
to announce support for the capability.Feel free to add suggestions to this list.
The text was updated successfully, but these errors were encountered: