Time Conditions are allowed to have Destination of self, creating loop and crashing Asterisk

We learned this lesson the hard way.  Time Conditions allows the Destination to point to itself as a destination.  This causes a loop that ultimately ends in Asterisk crashing.

In our case, we had a Holidays Time Condition that was supposed to go to a Open Hours Time Condition, but instead of pointing to the Open Hours Time Condition, it pointed to itself.

Obviously, this is human error.  It would be awesome if FreePBX could save us from this mistake in the future by omitting the current Time Condition, as well as any and all other Time Conditions that point to the current Time Condition (either as a matching or non-matching Destination), from the dropdown list of Time Condition Destinations available.  Doing so would keep others from having a miserable day like we had (and from us repeating this unfortunate mistake in the future).

Dave