We'll take a look. It's probably better if we can get this to have predicate methods like "play.should_gather_facts()" or something if we want to escape the need for having to repeat test-logic for it in the code every time this field is accessed. But that can wait.
On Sat, Mar 15, 2014 at 6:15 PM, Brian Coca <[email protected]> wrote: > I changed the settings, but kept the trinary boolean (I know it bugs you) > as I think it is the simplest implementation. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/e6739ee6-d363-4a3c-927d-9ea0ce2a9572%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/e6739ee6-d363-4a3c-927d-9ea0ce2a9572%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEVJ8QNUyVohCbjs1s8GaaGWpjxSqfm%3DJ%3Dy2kX6a3vEk1w3gJA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
