-
Notifications
You must be signed in to change notification settings - Fork 253
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
Project autoshim #163
Project autoshim #163
Conversation
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.
Awesome! Looks good to me overall. I just have some thoughts about how the autoshimming errors are displayed to the user, and maybe @dherman can weigh in on that as well.
In the call this morning, Michael raised a corner case I don't think the PR currently covers: running |
Missing dependencies are no longer reported as errors. |
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! still needs review from @dherman
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.
Looks awesome! I had one tiny nit but I can just do a followup commit.
|
||
/// Convert dependency names to the path to each project. | ||
fn get_dependency_path(&self, name: &String) -> PathBuf { | ||
// TODO(158): Add support for Yarn Plug'n'Play. |
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.
Nit: the convention we use is // ISSUE(158):
.
let errors = project.autoshim(); | ||
|
||
for error in errors { | ||
display_error(&error); |
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.
I think I'm starting to doubt the part of the exit codes RFC that says that we should preserve the exit code of the underlying tool even if extra logic afterwards fails. We don't need to block this PR on this, but I filed an RFC issue to follow up.
I pushed a change to the one nit ( |
This is a speculative implementation of RFC 23.
A notable change with this PR is the grammar for the
notion shim
command, which has been moved behind thenotion-dev
feature flag.notion shim
=>notion shim list
notion shim foo
=>notion shim create foo
notion shim foo --delete
=>notion shim delete foo