error locations and IDE diagnostics support about tera HOT 4 OPEN

What is the timeline for a beta/preview release of v2?

No timeline yet. I'll try to add functions/tests/filters soon so people can try with some real templates but can't say when I will have time

from tera.

That's coming in v2! Have a look at an error: https://github.com/Keats/tera2/blob/master/src/tests/snapshots/tera__tests__rendering__rendering_errors%40unknown_var.html.snap.
Can VSCode read that file/line/col format? I can change it

from tera.

Great news! thank you!
What is the timeline for a beta/preview release of v2?

re: the format: VS Code matchers are just regex with capture groups. So, I think we have two options here:

1. Have an output format that is really easy to parse, for example, all the above values joined by a common separator (:):

// A problem matcher definition in VS Code:

{
  "fileLocation": ["relative", "${workspaceFolder}"],
  "pattern": {
    // foo/bar.jinja2:10:1:10:22:error:Failed to parse this expression.’
    "regexp": "^([^:]+):([^:]+):([^:]+):([^:]+):([^:]+):([^:]+):(.+)$",
    "file": 1,
    "line": 2,
    "column": 3,
    "endLine": 4,
    "endColumn": 5,
    "severity": 6,
    "message": 7,
  }
}

2. Or the more configurable/extensible option, exposing these properties on the error types returned, and the user can format/print it however they think is useful. So that Tera doesn't need to be forced to support a specific format, or worry about breaking it in the future.

from tera.

Thank you for your efforts!

from tera.