Let read-only editors show problems

[buremba]

I'm working on an extension that lets users compile Jsonnet files and view them as read-only JSON files.

I would like to add support for JSON Schema to the JSON outputs so that if the output is not valid, VSCode highlights the errors in the output created as a virtual document by the custom content provider.

However; VSCode doesn't seem to validate read-only files so JSON schema validator doesn't work on virtual documents. When I convert the scheme to untitled, the validation does work but since the JSON outputs are idempotent (generated from Jsonnet files), I don't want to give the users the ability to edit/save the JSON output as the output is irrelevant.

I believe that the validation is useful for the read-only files as well. It would be great if we can disable the code actions and make the validation at least optional depending on how the extension creates the virtual documents.

[aeschli]

The JSON language server validates all documents of language id json and jsonc.
The problem view shows the errors, but not the editor.

[buremba]

I see, thanks for the info @aeschli. That explains why I started seeing the errors when I installed the extension usernamehw.errorlens.

[vscodebot]

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!

[bpasero]

I wouldn't even know where to start looking to do this, I have no clue how the editor decides to show errors or not. Back to other folks.