Hi, I'm not sure about the behavior behind sfCommandOption::PARAMETER_REQUIRED, but I think that meens your option must have a value : --my-option=foo.
However, it's will be weird to have a required option. By its very nature, an option should be "optional". So, you must consider using an argument instead. On Wed, Sep 30, 2009 at 9:19 AM, klemens_u <[email protected]> wrote: > > I tried to implement a task where I want to use a required option. > > When I call the task without giving the required option the task > doesn't complain about it. > > Is this a bug, or did I miss something? > > Thanks, Klemens > > > -- Noël GUILBERT http://www.noelguilbert.com/ http://www.sensiolabs.com http://www.symfony-project.com Sensio Labs Tél: +33 1 40 99 80 80 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
