Skip to content
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

fix(codelens): Apply commandArgs to run targets #408

Merged
merged 1 commit into from
Jul 23, 2024

Conversation

makestuff
Copy link
Contributor

Currently, commandArgs is only applied to debug, test and coverage targets, not run targets, which is inconsistent: clicking a "build" codelens for a component and then clicking a "run" codelens for a runnable target which depends on that component ends up rebuilding it with a different configuration (e.g debug/optimized, remote/local build). It would be much more consistent if commandArgs applied to run targets.

This fixes #394.

@vogelsgesang vogelsgesang changed the title <fix>(codelens): Apply commandArgs to run targets fix(codelens): Apply commandArgs to run targets Jul 20, 2024
@makestuff makestuff force-pushed the commandargs-for-run branch 2 times, most recently from 073a29b to cc5fe51 Compare July 20, 2024 19:43
@vogelsgesang vogelsgesang merged commit 9c77c18 into bazel-contrib:master Jul 23, 2024
2 checks passed
@makestuff makestuff deleted the commandargs-for-run branch July 23, 2024 04:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Why does commandArgs not apply to Run targets?
3 participants