harper-ls works only with comments?

[pratyushmittal]

It seems the harper-ls works only with comments.

The documentation mentions:

Out of the box, it has built-in support for parsing the comments of most programming languages, as well as any and all Markdown files.

The text inside HTML nodes is not checked. Is there any way to enable harper-ls on more tree-sitter grammars (such as strings)?

[mcecode]

It seems the harper-ls works only with comments.

It depends on the language. Maybe the documentation can be more clear on that, but if you look at the Supported Languages section of the doc, it shows which languages are comments only and which aren't. Generally, document-type languages like HTML, Markdown, and Typist are checked as a whole, while only comments are checked for programming languages like C, JavaScript, and Python.

The text inside HTML nodes is not checked.

It checks it on my end, though.

Maybe you haven't included HTML to be linted in your config? What editor are you using?

Is there any way to enable harper-ls on more tree-sitter grammars (such as strings)?

We currently don't support linting strings, but there is an open issue requesting that feature (#544). If there are other language constructs you'd like harper-ls to lint, feel free to open an issue, though I can't promise that it will be implemented right away.

[pratyushmittal]

Thanks a lot @mcecode for looking into it. The filetype in my case was htmldjango. Changing it to filetype=html made it show errors inside the tags. Can we configure harper-ls to treat htmldjango as html?

[mcecode]

Can we configure harper-ls to treat htmldjango as html?

I don't think we can just start treating htmldjango as html since it has constructs like tags ({% tag %}) that aren't present in HTML. We'll need to add explicit support for htmldjango. #79 is the issue we use to track language support. I'll add a comment there for you to request support. Feel free to chime in and join the discussion there.