-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
removes forc clean cargo toml error #945
Conversation
Produces an error rather than panicking when the user specifies a semver version which is currently unsupported. As mentioned at: #918 (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.
This should definitely be changed! Instead of removing (which would be better than simply commenting out), cargo clean
should not be ran at all if Cargo.toml
doesn't exist. The reason being that there might be other ways cargo clean
can fail, and we shouldn't silence those errors.
Thank you for clarifying! I'll get on this tomorrow morning. (commented out since I wasn't sure btw) |
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.
One last change, otherwise looking good!
Closes #932
I've updated the
find_manifest_dir
function to be dynamic, so that we can find either aForc.toml
orCargo.toml
, then used that function to check for aCargo.toml
and if one is not found, emit a non-error warning message that without onecargo clean
will be bypassed.