DevEx and QoL Improvements for Everyone ! #232
Description
Hi !
Just wanted to bring a few features that I thought would be great to bring to this extension as it lacks a few things, all things considered, when compared to other extensions.
This a non exhaustive list but a list nonetheless that will help give a few feedback on things that developers could tackle next !
I'm open to feedback at to what modify in this list.
Be aware that this is based on personal experience and as such very much so biased. These are inspired from personal experience as well as my day-to-day usage of the CMake Tools Extension. I know that this comparison is unfair but I love Zig so much that I really want to bring everything to the next level, but I'm unable as I lack the necessary skills.
As such, I will help with what I can by making a detailed and documented list !
- Adding running codelens above the main function of a program (see fig. 1 for example)
- Adding codelens above tests
- Parsing the tests in the vscode tests API, see fig. 5
- Parse and run the tests on a workspace level (aka. build.zig) by asking the user to add a corresponding build.zig implementation
- Add a status bar button to compile / run (quick fix as corresponding command is already implemented), see fig. 2 for detail image
- Being able to change zig version / release mode on the status bar (see fig. 3) (Easy fix as a versioning system is already implemented in introduce a fully featured version manager #230 !)
- Change the choice of the run artifact on the status bar (see fig. 4)
- Fix "Build workspace" provides no feedback #196 (quick fix, just outing the logs to a output channel)
Figures and illustrating images
fig.1 : Shamelessly copied and pasted from Zig Main Runner
fig. 2 : Shamelessly stolen from VSCode's docs
fig. 3 : Showcase of CMake's changing release type system
fig. 4 : Showcase of CMake's changing target system
fig. 5 : Showcase of running some tests on VSCode's API