Breaking changes in 'analyzer' package.

pkg/smoke/pubspec.yaml

Index: pkg/smoke/pubspec.yaml
diff --git a/pkg/smoke/pubspec.yaml b/pkg/smoke/pubspec.yaml
index 4beae18149b9d8589aa1a3d95e3d4a3531b01bd1..8770aff71d55d143162fd6a34376811d6f5a4acc 100644
--- a/pkg/smoke/pubspec.yaml
+++ b/pkg/smoke/pubspec.yaml
@@ -1,5 +1,5 @@
 name: smoke
-version: 0.2.0+3
+version: 0.2.0+4

[Siggi Cherem (dart-lang), 2014/08/06 03:07:22]

here too - 0.2.1-dev

[scheglov, 2014/08/06 18:03:50]

Done.

 author: Polymer.dart Authors <web-ui-dev@dartlang.org>
 homepage: "https://api.dartlang.org/apidocs/channels/be/#smoke"
 description: >
@@ -9,7 +9,7 @@ description: >
 dependencies:
   barback: ">=0.9.0 <0.16.0"
   logging: ">=0.9.0 <0.10.0"
-  analyzer: ">=0.13.0 <0.22.0"
+  analyzer: ">=0.22.0 <0.23.0"

[Siggi Cherem (dart-lang), 2014/08/06 03:07:22]

mmm, this is a bit unfortunate, since public APIs from smoke don't break, only
tests are affected. While technically that is still a break, our public code
still supports using analyzer >=0.13.0 < 0.23.0.

This might not be worth it, but is it possible to make this a backwards
compatible change? For example, if we add the API with a different name
(resolveRelativeUri) and leave the old API unused, we would still have a
breaking change, but it would let us have smoke and code_transformers continue
to work with old versions of the analyzer at the same time.

Thoughts?

[scheglov, 2014/08/06 18:03:50]

  Done.
  I will let Brian to decide this API question.

 # TODO(sigmund): once we have some easier way to do global app-level
 # transformers, we might want to remove this transformer here and only apply it
 # in apps that need it.