Fields, getters and setters documented as properties.

pkg/dartdoc/lib/src/client/client-shared.dart

Index: pkg/dartdoc/lib/src/client/client-shared.dart
diff --git a/pkg/dartdoc/lib/src/client/client-shared.dart b/pkg/dartdoc/lib/src/client/client-shared.dart
index bddaa1226c46821ec37b15b312270bae84989c9c..a448ae2765bb89daba8549f701996f4beda7c268 100644
--- a/pkg/dartdoc/lib/src/client/client-shared.dart
+++ b/pkg/dartdoc/lib/src/client/client-shared.dart
@@ -38,18 +38,20 @@ enableCodeBlocks() {
     // disabled.
     if (showCode == null) continue;
 
-    var pre = elem.query('pre.source');
+    var preList = elem.queryAll('pre.source');

[Bob Nystrom, 2012/10/11 17:04:21]

Nit, I would prefer "pres" or "sources" over "preList". For collection objects,
I prefer just using a plural name over mentioning the concrete collection type,
unless that really matters.

[Lasse Reichstein Nielsen, 2012/10/12 09:47:26]

Agree, and the HTML tag seems less interesting than the class in describing the
elements, so "sources".

 
     showCode.on.click.add((e) {
-      if (pre.classes.contains('expanded')) {
-        pre.classes.remove('expanded');
-      } else {
-        // Syntax highlight.
-        if (!pre.classes.contains('formatted')) {
-          pre.innerHTML = classifySource(pre.text);
-          pre.classes.add('formatted');
-        };
-        pre.classes.add('expanded');
+      for (final pre in preList) {
+        if (pre.classes.contains('expanded')) {
+          pre.classes.remove('expanded');
+        } else {
+          // Syntax highlight.
+          if (!pre.classes.contains('formatted')) {
+            pre.innerHTML = classifySource(pre.text);
+            pre.classes.add('formatted');
+          };
+          pre.classes.add('expanded');
+        }
       }
     });
   }