I suggest you ...

Add more detailed messages for the unhandled trigger InvalidOperationException.

It would be nice to be able to distinguish whether an unhandled trigger InvalidOperationException was caused due to no triggerBehaviour configured or if the guard condition caused the InvalidOperationException. This would allow for easier diagnostics and more meaningful reporting of issues.

I think this could be easily achieved by add a property similar to the PermittedTriggers, that excludes the IsGuardConditionMet checks.
e.g. ConfiguredTriggers

so when an InvalidOperationException occurs, you can easily tell if it was a guard that caused the failure by checking if the current trigger is in the ConfiguredTriggers.

6 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    PeterPeter shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base