-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zig Run and Zig Test run actions should be able to utilize build.zig dependencies #48
Comments
You can use the green arrow run button in build.zig if you want to run |
Thanks. I realise this, but it means the granularity of running individual tests from the files themselves, which is often useful as part of a development iteration loop, is lost. Oh well. |
I'll look into implementing some sort of custom build runner into zigbrains in a future release that can utilize build.zig dependencies for the in-file run buttons (similarly to what intellij already does with gradle/maven java projects) |
As a rough idea/draft of this feature, here's a concept for how dependency discovery would be done for the tests:
The ZB build runner would then just create a single-file test step in the background with the discovered dependencies and use that for the test run buttons. (As an added bonus, a custom build runner would also make |
That all sounds awesome. I appreciate how 'young' all of this is - ZigBrains lets so many people learn and grow with Zig within a familiar environment, and enhancements like this will really help. |
Similar to #41, when there are build dependencies, the 'Green Arrows' in the margins to run code/tests will fail, as they rely on the run configuration.
Is there any way to repurpose these to use the build pipeline instead, or is it a limitation of the IDE that means we cannot use the margin-based runners ? (Basically is it possible to optionally replace all usages of 'run' configurations with 'build' configurations ?
The text was updated successfully, but these errors were encountered: