I mean the configurable block on the old front. That is included or excluded in a way that is external to the trailblock definition. My objection is the `RunningOrderTrailblockDescriptionSwitch` class is modal. It does one thing some of the time and then other stuff the rest of the time. This is an anti-pattern. GoF treat this with the State Pattern instead.

I would prefer this to be treated in the same style as the configurable block on old fronts. i.e. inclusion/exclusion made entirely external to the trailblock classes.

I don't think it needs to be more complicated than a test in a template somewhere:

   @if (australia and switch is on) {
      etc etc
   }

This is for a small test in the old fronts that will be burned down in favour of the facia stuff. Achieving this requirement should not pollute the common model classes like this.