-
Notifications
You must be signed in to change notification settings - Fork 124
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
[Question]: Should clear=true
on a task also clear the env of the task?
#816
Comments
thanks @Javagedes for reporting. |
@Javagedes sorry for the really really late reply. |
cargo-make is now released with this fix. thanks for reporting and please try it out. |
Describe The Bug
In our current project, we override the pre-made common tasks (Build, Test, Coverage) with our own custom tasks, setting
clear = true
in the task as the documentation specifies that this deletes the existing task attributes. I personally read this as we are not extending the task, but completely overwriting it so only our task remains.However, I'm experiencing an issue where my override of the coverage task fails when named coverage, but succeeds when named coverage2, hinting that some information from the old task remains.
Here is the task i'm referring to:
I performed a
cargo make --print-steps coverage
to see if there was any difference, which there was:when named coverage
when named coverage2
I don't have an argument one way or the other if
clear = true
fully or partially overrides, but I just wanted to raise this issue to make sure that what I'm seeing is not a bug. If it is not a bug, I do think it could be documented a bit better as to whatclear = true
actually does.Thanks for your time :)
The text was updated successfully, but these errors were encountered: