Add DAP locator that will auto-convert zig build into debug session #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
osiewicz
reviewed
Sep 16, 2025
osiewicz
reviewed
Sep 17, 2025
Merged
kubkon
added a commit
that referenced
this pull request
Sep 17, 2025
Extracted from #10 Implements custom tasks: * `zig build test` * `zig build run` * `zig test $ZED_FILE --test-filter $ZED_CUSTOM_ZIG_TEST_NAME` - which runs during runnable code detection
kubkon
force-pushed
the
better-dap-config
branch
from
17ccb2b to
f57d6af
Compare
kubkon
changed the title
osiewicz
reviewed
Sep 18, 2025
| .and_then(|cwd| Some(Path::new(&cwd).file_name()?.to_string_lossy().into_owned())) | ||
| } | ||
|
|
||
| fn get_test_exe_path() -> Option<String> { |
Contributor
There was a problem hiding this comment.
This will trip over itself the moment somebody runs two tests (possibly in unrelated projects) concurrently. :/ Could we include some kind of disambiguator here?
Contributor
Author
There was a problem hiding this comment.
That's a good catch. Originally I wanted to use project name but CWD is not set at this point. However, thinking about it some more, maybe use UUID that will persist for the duration of this debugging session or something? Kinda feels like reimplementing compiler's caching logic...
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A couple of notable changes that will land as part of this PR:
std::env::current_dir()handling on Windows hostExtensiontrait, and in particulardap_locator_create_scenarioandrun_dap_locatorzig build runandzig build testdirectly from the command palettezig build runandzig test --test-filterinto a debug scenario both of which can be triggered at the GUI level via run/debug markersThis final step comes with a caveat for
zig build run, namely, it assumes the project has been created withzig initand the project name matches the executable name. I think this is a fair assumption. In other cases, for more elaborate/custom projects I think it is reasonable to expect the user to create a custom debug config.TODO: