Add context to OptionsProcessor callback API.

pkg/analyzer/lib/plugin/options.dart

 // Copyright (c) 2015, 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.
 
 /// Support for client code that wants to consume options contributed to the
 /// analysis options file.
 library analyzer.plugin.options;
 
+import 'package:analyzer/src/generated/engine.dart';
 import 'package:analyzer/src/plugin/options_plugin.dart';
 import 'package:plugin/plugin.dart';
 import 'package:yaml/yaml.dart';
 
 /// The identifier of the extension point that allows plugins to access
 /// options defined in the analysis options file. The object used as an
 /// extension must be an [OptionsProcessor].
 final String OPTIONS_PROCESSOR_EXTENSION_POINT_ID = Plugin.join(
     OptionsPlugin.UNIQUE_IDENTIFIER,
     OptionsPlugin.OPTIONS_PROCESSOR_EXTENSION_POINT);
@@ skipping 22 matching lines @@
 /// matter of inspecting the parsed nodes.  For example, testing whether the
 /// compiler's resolver is set to use the `useMultiPackage` option might look
 /// something like this (eliding error-checking):
 ///
 ///     bool useMultiPackage =
 ///         options['compiler']['resolver']['useMultiPackage'];
 abstract class OptionsProcessor {
   /// Called when an error occurs in processing options.
   void onError(Exception exception);
 
-  /// Called when the options file is processed.
+  /// Called when an options file is processed.
   ///
   /// The options file is processed on analyzer initialization and
   /// subsequently when the file is changed on disk.  In the event of a
   /// change notification, note that the notification simply indicates
   /// a change on disk. Content in specific option scopes may or may not
   /// be different. It is up to the implementer to check whether specific
-  /// options have changed and to handle those changes appropriately.
-  void optionsProcessed(Map<String, YamlNode> options);
+  /// options have changed and to handle those changes appropriately. In
+  /// addition to the [options] map, the associated analysis [context] is
+  /// provided as well to allow for context-specific configuration.
+  void optionsProcessed(Map<String, YamlNode> options, AnalysisContext context);

[Brian Wilkerson, 2015/10/08 16:46:47]

nit: In general, I like putting collection-valued arguments last because
invocations of the function format better when the collection is a literal.
Probably only applies to test code in this case, but...

[pquitslund, 2015/10/08 17:09:05]

Will do!

 }