Switch transformers over to source_span

pkg/polymer/pubspec.yaml

Index: pkg/polymer/pubspec.yaml
diff --git a/pkg/polymer/pubspec.yaml b/pkg/polymer/pubspec.yaml
index 6b35dc86589dff1e6280625bfdefca5aefc22580..af1207787c23db428ec33d63db196df83c0c924d 100644
--- a/pkg/polymer/pubspec.yaml
+++ b/pkg/polymer/pubspec.yaml
@@ -12,7 +12,7 @@ dependencies:
   barback: '>=0.9.0 <0.15.0'
   browser: '>=0.10.0 <0.11.0'
   code_transformers: '>=0.1.4 <0.2.0'
-  html5lib: '>=0.11.0 <0.12.0'
+  html5lib: '>=0.11.0 <0.13.0'

[Siggi Cherem (dart-lang), 2014/07/29 20:56:32]

There are a couple changes we need in polymer too, otherwise this might break in
checked mode. Here are the cases I've found:

pkg/polymer/lib/src/build/:
 - linter.dart: line 133, 385
 I think removing the types there should fix it here.

 - import_inliner.dart: 425
 Same here, but this one is tricky because this file creates old-style spans and
will pass them here, so `_newUrl` would need to accept both.

 - script_compactor.dart: 505
 We can delete the whole function, it seems like dead code.

I believe running the transformer tests (pkg/polymer/test/build/) will help
catch any other issues.

[nweiz, 2014/07/29 21:13:17]

I hadn't realized that these spans were transitively passed to barback. In that
case, I'll wait on this CL until barback support for source_span has landed.
Once it has, I'll switch the transformers entirely over to source_span as well.

[Siggi Cherem (dart-lang), 2014/07/29 21:21:08]

Ah - ok, I didn't know barback didn't have the support yet. Yes, most of the
spans in html5lib end up being passed to the barback loggers.

   logging: '>=0.9.0 <0.10.0'
   observe: '>=0.12.0-dev <0.13.0'
   path: '>=0.9.0 <2.0.0'