• Kevin Lau's avatar
    Clarify operator docs wording · bb69a1ed
    Kevin Lau authored
    The original is explaining the negation, when the body would not be
    included. Which would happen in the complement of the if expression,
    ie. flipped by De Morgan's law's:
    
    ```
    not (or .Values.anUnsetVariable (not .Values.aSetVariable))
    ==
    and (not .Values.anUnsetVariable) .Values.aSetVariable
    ```
    
    > unset variables evaluate to false
    
    is equivalent to `not .Values.anUnsetVariable`.
    
    > and
    
    is equivalent to `and`.
    
    > .Values.setVariable was negated with the not function
    
    doesn't seem to match `.Values.aSetVariable`.
    To me, that would be `not .Values.aSetVariable` instead.
    
    Anyway, explaining the `if` expression as-is and not the negation is
    clearer and parallels the first `if` operator.
    Signed-off-by: 's avatarKevin Lau <kelau1993@gmail.com>
    bb69a1ed
Name
Last commit
Last update
.circleci Loading commit data...
.github Loading commit data...
_proto Loading commit data...
cmd Loading commit data...
docs Loading commit data...
pkg Loading commit data...
rootfs Loading commit data...
scripts Loading commit data...
testdata Loading commit data...
.gitignore Loading commit data...
CONTRIBUTING.md Loading commit data...
KEYS Loading commit data...
LICENSE Loading commit data...
Makefile Loading commit data...
OWNERS Loading commit data...
README.md Loading commit data...
SECURITY_CONTACTS Loading commit data...
code-of-conduct.md Loading commit data...
glide.lock Loading commit data...
glide.yaml Loading commit data...
versioning.mk Loading commit data...