Description

The #[IsEnabled] attribute is really helpful but can't help with negated flags, such as kill switches. The #[IsNotEnabled] attribute introduced in this PR aims to fill the need, by just reversing the throwing logic, but keep reusing the infrastructure already in place.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

• Unit tests
• Spec Tests
• Integration tests / Manual Tests

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

NB: I couldn't find the tests in this repo, did I miss something ?