File level Diagnostic reporting

[prmichaelsen]

I would like to supply file level diagnostics, eg

  const diagnosticsCollection = languages.createDiagnosticCollection("Datapath Lint");
  // Applies to entire file, no line number/range is applicable
  diagnosticCollection.set(uri, new Diagnostic(
    message,
    DiagnosticSeverity.Error,
  )); 

Instead of

  const diagnosticsCollection = languages.createDiagnosticCollection("Datapath Lint");
  diagnosticCollection.set(uri, new Diagnostic(
    range,
    message,
    DiagnosticSeverity.Error,
  )); 

Currently, the workaround I am using is

  const diagnosticsCollection = languages.createDiagnosticCollection("Datapath Lint");
  diagnosticCollection.set(uri, new Diagnostic(
    new Range(0, 0, 0, 0),
    message,
    DiagnosticSeverity.Error,
  )); 

This enables the issue to show up in the Problems tab, but does not
look very sophisticated in the file itself.

The issue is the underlying linter I am using to generate the diagnostics
does not support reporting the line numbers generating the errors.

Thank you,
Patrick

[vs-code-engineering]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vs-code-engineering]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vs-code-engineering]

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!