Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Split config.changed into changed and new #61
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
johnsca commentedApr 22, 2016
While it can be argued that config values are "changing" from not having
a previous value in the very first hook that's fired, not distinguishing
that from a "real" change (that is, the config had a definite value
previously and has a new definite value now) makes certain constructs
difficult. On the other hand, it is relatively easy to go the other
way using
@when_any.For example:
Without the distinction,
installwill end up being called twice.