-
Notifications
You must be signed in to change notification settings - Fork 368
DevContainer commands now default the workspace folder to the current directory if not specified. #1104
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
DevContainer commands now default the workspace folder to the current directory if not specified. #1104
Conversation
chrmarti
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks! Left a few comments.
Co-authored-by: Josh Wiley <josh@cloudbend.dev>
chrmarti
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks!
abdurriq
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM apart from the test assertions which should not be in the try-catch blocks, else the tests will pass if the assertions are skipped due to something failing earlier in the try-catch block.
Fixes: #1069
Issue summary:
This PR enhances the user experience by automatically defaulting the [--workspace-folder] parameter to the current working directory when it is not explicitly specified. The following DevContainer CLI commands will now use the current working directory as the default workspace folder if [--workspace-folder] is omitted:
Test cases is implemented for all these commands