Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve handling of notification rules we can't parse #1399

Merged
merged 1 commit into from
Apr 15, 2016

Conversation

richvdh
Copy link
Member

@richvdh richvdh commented Apr 15, 2016

  • An absent rule is the same as a rule with 'enabled == false', and is not
    necessarily 'OFF' (particularly in the case of the bot rule, which is
    inverted).
  • If we don't understand the rule, then don't tick any of the radio buttons,
    and instead show it in the 'external' section.

Fixes #1348

* An absent rule is the same as a rule with 'enabled == false', and is not
necessarily 'OFF' (particularly in the case of the bot rule, which is
inverted).

* If we don't understand the rule, then don't tick any of the radio buttons,
and instead show it in the 'external' section.
@dbkr
Copy link
Member

dbkr commented Apr 15, 2016

Possibly would be better to do refactors separately from logic fixes as it's hard to see what the logic fix is here. I think this is fine though.

@dbkr dbkr merged commit 57c7d81 into develop Apr 15, 2016
@richvdh richvdh deleted the rav/fix_unparsable_notifications branch August 10, 2016 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants