Morgante Pell

@jmqd Just checking - need any further advice on this?

Hi @hyunbinseo, did you try the [Grit version](https://docs.grit.io/registry/github.com/fabian-hiller/valibot/migrate_to_v0_31_0)? It isn't sensitive to the comment issue.

If you want patterns to be enforced by `grit check` you need to add an enforcement level of at least `warn`: https://docs.grit.io/guides/config#patterns You can see some examples in this repo:...

The easiest solution is changing `grammar.js` but ideally we would fix spacing for children as well.

This is from the legacy where we originally had a different (Node) CLI that was talking to the "Marzano" Rust binary, but I agree it's confusing at this point and...

> About that "marzano", some examples contain `engine marzano(0.1)` as the first line. Is that necessary? Does it change anything? It doesn't currently change anything, but does indicate the version...

Thanks for your interest! We currently prioritize languages for our commercial customers, but if you'd like to take on adding this yourself the process is described here: https://github.com/getgrit/gritql/blob/main/CONTRIBUTING.md#adding-a-new-target-language

The problem is usually [missing contexts](https://github.com/getgrit/gritql/blob/main/CONTRIBUTING.md#snippet-contexts). If you open a draft PR I'm happy to try debugging.

Thanks for the report, I think this is an upstream error in the typescript grammars: https://github.com/tree-sitter/tree-sitter-typescript Note Grit will still do a best effort attempt even on files that fail...

Please share the output of `grit doctor` and a (redacted) copy of the file you're trying to run on.