Move commit list out its own model.

Tools/GardeningServer/ui/ct-failure-stream.html

 <!--
 Copyright 2014 The Chromium Authors. All rights reserved.
 Use of this source code is governed by a BSD-style license that can be
 found in the LICENSE file.
 -->
 
 <link rel="import" href="ct-failure-card.html">
+<link rel="import" href="../model/ct-commit-list.html">
 
-<polymer-element name="ct-failure-stream" attributes="groups commits tree" noscript>
+<polymer-element name="ct-failure-stream" attributes="groups commits tree">
   <template>
     <style>
       :host {
         display: block;
       }
 
       ct-failure-card {
         margin: 5px;
         padding: 5px;
         border-top: 1px solid lightgrey;
       }
     </style>
     <template repeat="{{ group in groups }}">
-      <ct-failure-card group="{{ group }}" commits="{{ commits }}" tree="{{ tree }}"></ct-failure-card>
+      <ct-failure-card group="{{ group }}" commitList="{{ _commitList(group) }}" tree="{{ tree }}"></ct-failure-card>
     </template>
   </template>
+  <script>
+  Polymer({
+    _commitList: function(group) {
+      return new CTCommitList(group, this.commits);

[ojan, 2014/08/12 21:08:36]

Not sure if it's better, but CTFailureGroup could have a commitlist method that
you call here. Then you could keep passing commits down to ct-failure-card and
ct-failure-card would pass group.commitList(this.commits) to ct-commit-list. The
marginal advantage I see to that is that ct-failure-stream doesn't need to know
about CTCommitLists at all, e.g. this would make testing easier.

Up to you.

[dsinclair, 2014/08/15 14:05:04]

Done.

+    }
+  });
+  </script>
 </polymer-element>