Why treat --force differently?

[Silex]

Hello,

At https://github.com/erikhuda/thor/blob/master/lib/thor/parser/option.rb#L89, you can see that the --force option doens't have its --no-force option generated.

1. Why treat it differently?
2. How can I achieve the same behavior? I don't want these --no-foo aliases.

[webdestroya]

I have this exact same problem, I have flags like --pretend which seems pointless to create a --no-pretend, when the "no pretend" should just be "don't put a flag"

It would be nice to have an option on the method_option block that lets you disable the anti-flag

[afeld]

Duplicate of #417.

[Silex]

#417 only covers 2.

I think once #417 is fixed, we need to fix 1. and not treat --force differently.

[ddarbyson]

@webdestroya I agree, has this been fixed at all? I would like to only use --myoption without the inverted --no-pretend option

[rafaelfranca]

Force is an internal option and you can't inverse it with a --no- option and this is why it is treaded differently. We will track #417 for disabling this feature for users options.