title: ngInclude fallback template
body: <p>Is there a best-practice for falling back on <code>ngInclude</code>? </p>
  
  <p>The initial solution I came up with was for the controller (or parent directive, where applicable) to have something along the lines of</p>
  
  <pre><code>scope.someInclude = 'views/x/custom/'+someVar+'.html';
  
  scope.$on('$includeContentError', function(event, failedTemplate){
      if(scope.someInclude === failedTemplate){
          scope.someInclude = 'views/x/default.html';
      }
  });
  </code></pre>
  
  <p>Where the template would simply <code>ng-include='someInclude'</code>.</p>
  
  <p>This doesn't seem like a great solution for several reasons. Among the largest of which being that it won't remember which templates don't work, along with the extra boilerplate. </p>
  
  <p>Before I go building a service to alleviate some of these things, are there any simpler solutions that I'm missing?</p>