-
Notifications
You must be signed in to change notification settings - Fork 121
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
force
is not very self-explaining
#120
Comments
agree allow_failure is much better and self explanatory, I kinda reused the 'force' name from other tools I saw such as gruntjs. |
You could break it with 1.0. IMO situations like these are the reason why
we have pre-1.0 releases :)
But, obviously it is totally up to you!
Also, I guess that the use of force = true is rather rare. Maybe 1 or 2 per
codebase? Fixing that takes literally 10 seconds if the error message is
good :)
…On Mon, 29 Oct 2018, 20:07 Sagie Gur-Ari, ***@***.***> wrote:
agree allow_failure is much better and self explanatory, I kinda reused
the 'force' name from other tools I saw such as gruntjs.
unfortunately, changing this would be a real backward break and i'm not
sure its important enough to justify it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#120 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFO3NRTwjvXx9AnuGpCT-CjcESG4e9yJks5upsVugaJpZM4X-oSn>
.
|
fixing takes little time, understanding why takes longer and it would increase user frustration. I'll think about it. for now I'm keeping this item open. |
That is why I added "if the error message is good"! Was thinking about something like Thanks for considering it! :) |
@thomaseizinger I decided to go for it. I renamed it to ignore_errors. |
@thomaseizinger published 0.16.8 so closing this issue. |
Awesome! |
Problem Description
The
force
argument of a task is not very self-explaining. I had to check the documentation on what it does.Maybe a name like
allow_failure
orignore_failure
could express the intent more clearly?Code Example
The text was updated successfully, but these errors were encountered: