VSCode compatible hyperlinks in terminal output for compilation errors#21
VSCode compatible hyperlinks in terminal output for compilation errors#21deldrid1 wants to merge 1 commit intoelectricimp:masterfrom
Conversation
<path>:<line>:<column>
|
Thank you @deldrid1! I'll grab it from here. I would also like to hear more about your best practices of developing EI projects in the VS Code. Are there any tricks that you can share? I would like to make it an officially supported/recommended option to the Sublime Text Plugin. |
|
Probably would be best to setup a phone call? Do you want to reach out via email? As a high level comment, I would love for VSCode to be an officially supported first-party “thick” client solution with full impCentral UI capability, plus more! I think between imp-central-api, imp-central-impt, Builder, and the impCentral web page, most of the hooks are already there.... In case you get bored: |
|
Yes, definitely let's discuss this! Thanks, @deldrid1 |
|
As we have vscode extension implemented, is this still relevant? |
@ppetrosh - this PR provides an update that allows for
impt build runsquirrel compilation errors to be clickable in VSCode via<path>:<line>:<column>syntax ala https://code.visualstudio.com/updates/v1_12#_integrated-terminal-link-line-and-column-ranges. This makes the errors much more useful/productive as you don't have to go chase them down in code.This is just a simple proof of concept that should be extended properly - not being familiar with Yargs, this code base is a bit tough for me to navigate as far as development goes, but hopefully this gives you enough of an idea of what would need to happen to pull it in?
In a future state, this would actually link you to the builder source files in addition to the built file - I'm hoping your much more familiar with the structure of the impt code base and thats something you could add!