Fix vscode rdbg launch command #8778
Merged
Conversation
This file contains 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
JamieMagee
force-pushed
the
jamiemagee/rspec-launch
branch
from
6c15877
to
cc108fb
Compare
ryanbrandenburg
approved these changes
Jan 12, 2024
abdulapopoola
approved these changes
Jan 12, 2024
deivid-rodriguez
approved these changes
Jan 15, 2024
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.
The
omnibusdirectory doesn't include.bundle/bin/rspecanymore, so I use therspeccommand from$PATHinstead. I also changed it to run the current file by default, instead of asking you to input the file path.I also moved the tests command to the top of the list, so it runs by default when hitting F5. I think it's more common than debugging
dry-run.rb.