Add a note about not importable annotations

source_gen/CHANGELOG.md

@@ -1,7 +1,10 @@
+## 1.3.1-dev
+
 ## 1.3.0
 
-* Add support for `build_extensions` configuration of builders producing multiple files. Eg:
-  `build_extensions: { '.dart': ['.stub.dart', '.web.dart', '.vm.dart'] }`
+* Add support for `build_extensions` configuration of builders producing
+  multiple files. Eg: `build_extensions: { '.dart': ['.stub.dart', '.web.dart',
+  '.vm.dart'] }`
 
 ## 1.2.7
 
@@ -39,6 +42,7 @@
   represents their type. Previously we checked this pattern only for enums,
   however there are enum-like usages in classes which are not enums.
 - Allow the latest version of `package:analyzer`.
+>>>>>>> master
 
 ## 1.2.0
 

source_gen/lib/src/generator_for_annotation.dart

@@ -39,7 +39,14 @@ import 'type_checker.dart';
 /// extension, are not searched for annotations. To operate on, for instance,
 /// annotated fields of a class ensure that the class itself is annotated with
 /// [T] and use the [Element] to iterate over fields. The [TypeChecker] utility
-/// may be helpful to check which elements have a given annotation.
+/// may be helpful to check which elements have a given annotation if the
+/// generator should further filter it's target based on annotations.
+///
+/// If the annotation type cannot be imported on the Dart VM, for example if it
+/// imports `dart:html` or `dart:ui`, then the default behavior of using
+/// `TypeChecker.fromRuntime` is not feasible. In these cases extend
+/// `GeneratorForAnnotation<void>` and override the [typeChecker] member with a
+/// checker matching the annotation type.
 abstract class GeneratorForAnnotation<T> extends Generator {
   const GeneratorForAnnotation();
 

source_gen/pubspec.yaml

@@ -1,5 +1,5 @@
 name: source_gen
-version: 1.3.0
+version: 1.3.1-dev
 description: >-
   Source code generation builders and utilities for the Dart build system
 repository: https://github.com/dart-lang/source_gen/tree/master/source_gen