pkg/polymer builder.dart doc tweaks

pkg/polymer/lib/builder.dart

 // Copyright (c) 2012, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 /**
  * Common logic to make it easy to run the polymer linter and deploy tool.
- * 
+ *
  * The functions in this library are designed to make it easier to create
  * `build.dart` files. A `build.dart` file is a Dart script that can be invoked
  * from the command line, but that can also invoked automatically by the Dart
  * Editor whenever a file in your project changes or when selecting some menu
  * options, such as 'Reanalyze Sources'.
  *
  * To work correctly, place the `build.dart` in the root of your project (where
  * pubspec.yaml lives). The file must be named exactly `build.dart`.
  *
  * It's quite likely that in the near future `build.dart` will be replaced with
@@ skipping 14 matching lines @@
  *        lint();
  *     }
  *
  * **Example 2**: Runs the linter and creates a deployable version of the app
  * every time.
  *
  *     import 'dart:io';
  *     import 'package:polymer/builder.dart';
  *
  *     main() {
- *        lint().then(() => deploy());
+ *        lint().then((_) => deploy());
  *     }
  *
  * **Example 3**: Runs the linter, but conditionally does the deploy step. See
  * [parseOptions] for a description of options parsed automatically by this
  * helper library.
  *
  *     import 'dart:io';
  *     import 'package:polymer/builder.dart';
  *
  *     main() {
  *        var options = parseOptions();
- *        lint().then(() {
+ *        lint().then((_) {
  *          if (options.forceDeploy) deploy();
  *        });
  *     }
  *
  * **Example 4**: Same as above, but uses [build] (which internally calls [lint]
  * and [deploy]).
  *
  *     import 'dart:io';
  *     import 'package:polymer/builder.dart';
  *
@@ skipping 25 matching lines @@
 
 
 /**
  * Runs the polymer linter on any relevant file in your package, such as any
  * .html file under 'lib/', 'asset/', and 'web/'. And, if requested, creates a
  * directory suitable for deploying a Polymer application to a server.
  *
  * The [entryPoints] list contains files under web/ that should be treated as
  * entry points. Each entry on this list is a relative path from the package
  * root (for example 'web/index.html'). If null, all files under 'web/' are
- * treated as possible entry points. 
+ * treated as possible entry points.
  *
  * Options are read from the command line arguments, but you can override them
  * passing the [options] argument. The deploy operation is run only when the
  * command-line argument `--deploy` is present, or equivalently when
  * `options.forceDeploy` is true.
  *
  * The linter and deploy steps needs to know the name of the [currentPackage]
  * and the location where to find the code for any package it depends on
  * ([packageDirs]). This is inferred automatically, but can be overriden if
  * those arguments are provided.
  */
 Future build({List<String> entryPoints, CommandLineOptions options,
     String currentPackage, Map<String, String> packageDirs}) {
   if (options == null) options = _options;
   return lint(entryPoints: entryPoints, options: options,
       currentPackage: currentPackage, packageDirs: packageDirs).then((res) {
     if (options.forceDeploy) {
       return deploy(entryPoints: entryPoints, options: options,
           currentPackage: currentPackage, packageDirs: packageDirs);
     }
   });
 }
 
 
 /**
- * Runs the polymer linter on any relevant file in your package, 
+ * Runs the polymer linter on any relevant file in your package,
  * such as any .html file under 'lib/', 'asset/', and 'web/'.
  *
  * The [entryPoints] list contains files under web/ that should be treated as
  * entry points. Each entry on this list is a relative path from the package
  * root (for example 'web/index.html'). If null, all files under 'web/' are
- * treated as possible entry points. 
+ * treated as possible entry points.
  *
  * Options are read from the command line arguments, but you can override them
  * passing the [options] argument.
  *
  * The linter needs to know the name of the [currentPackage] and the location
  * where to find the code for any package it depends on ([packageDirs]). This is
  * inferred automatically, but can be overriden if those arguments are provided.
  */
 Future lint({List<String> entryPoints, CommandLineOptions options,
     String currentPackage, Map<String, String> packageDirs}) {
@@ skipping 34 matching lines @@
 
 /**
  * Creates a directory suitable for deploying a Polymer application to a server.
  *
  * **Note**: this function will be replaced in the future by the `pub deploy`
  * command.
  *
  * The [entryPoints] list contains files under web/ that should be treated as
  * entry points. Each entry on this list is a relative path from the package
  * root (for example 'web/index.html'). If null, all files under 'web/' are
- * treated as possible entry points. 
+ * treated as possible entry points.
  *
  * Options are read from the command line arguments, but you can override them
  * passing the [options] list.
  *
  * The deploy step needs to know the name of the [currentPackage] and the
  * location where to find the code for any package it depends on
  * ([packageDirs]). This is inferred automatically, but can be overriden if
  * those arguments are provided.
  */
 Future deploy({List<String> entryPoints, CommandLineOptions options,
@@ skipping 85 matching lines @@
   if (res['help']) {
     print('A build script that invokes the polymer linter and deploy tools.');
     print('Usage: dart build.dart [options]');
     print('\nThese are valid options expected by build.dart:');
     print(parser.getUsage());
     exit(0);
   }
   return new CommandLineOptions(res['changed'], res['removed'], res['clean'],
       res['full'], res['machine'], res['deploy'], res['out']);
 }