Skip to content
This repository has been archived by the owner on Feb 23, 2019. It is now read-only.

Editor Markers #2

Open
karai17 opened this issue Jul 29, 2016 · 4 comments
Open

Editor Markers #2

karai17 opened this issue Jul 29, 2016 · 4 comments

Comments

@karai17
Copy link
Contributor

karai17 commented Jul 29, 2016

It would be helpful to have little tokens within the editor to show you where an error or linting issue is.

@nbredikhin
Copy link
Owner

I'm not sure that there is an API for that in vscode. If you have any information about it, let me know

@karai17
Copy link
Contributor Author

karai17 commented Jul 29, 2016

According to the following, it seems you can create/manage your own set of markers by creating a DiagnosticCollection, but there is not currently an API for managing all markers/getting other DiagnosticCollections in the editor. However, that might be enough?

microsoft/vscode#7232

https://code.visualstudio.com/docs/extensionAPI/vscode-api#DiagnosticCollection

https://code.visualstudio.com/docs/extensionAPI/vscode-api#Diagnostic

@karai17 karai17 changed the title In-editor error tokens Editor Markers Jul 29, 2016
@nbredikhin
Copy link
Owner

I still can't find an API documentation or code example for managing markers 🙈

@karai17
Copy link
Contributor Author

karai17 commented Jul 30, 2016

The links I provided should help (though the page loads poor, you'll need to ctrl+f). It seems liek you want to create a DiagnosticsCollection and then feed it Diagnostics objects for each issue LuaCheck gives you. Diagnostics seem to also have various severities (error, hint, information, warning) which could be helpful, depending on how LuaCheck gives you the information...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants