build_resolvers 1.0.1

Resolve Dart code in a Builder

1.0.1

• Fix a bug causing crashes on windows.

1.0.0

• Migrate to AnalysisDriver. There are behavior changes which may be breaking. The LibraryElement instances returned by the resolver will now:
  • Have non-working context fields.
  • Have no source offsets for annotations or their errors.
  • Have working session fields.
  • Have Source instances with different URIs than before.
  • Not include missing libraries in the importedLibraries getter. You can instead use the imports getter to see all the imports.

0.2.3

• Update to build 1.1.0 and add assetIdForElement.

0.2.2+7

• Updated _AssetUriResolver to prepare for a future release of the analyzer.
• Increased the upper bound for package:analyzer to <0.35.0.

0.2.2+6

• Increased the upper bound for package:analyzer to '<0.34.0'.

0.2.2+5

• Increased the upper bound for the build to <1.1.0.

0.2.2+4

• Removed dependency on cli_util.
• Increased the upper bound for the build to <0.12.9.

0.2.2+3

• Don't log a severe message when a URI cannot be resolved. Just return null.

0.2.2+2

• Use sdk summaries for the analysis context, which makes getting the initial resolver faster (reapplied).

0.2.2+1

• Restore new keyword for a working release on Dart 1 VM.

0.2.2

• Use sdk summaries for the analysis context, which makes getting the initial resolver faster.
• Release broken on Dart 1 VM.

0.2.1+1

• Increased the upper bound for the sdk to <3.0.0.

0.2.1

• Allow passing in custom AnalysisOptions.

0.2.0+2

• Support package:analyzer 0.32.0.

0.2.0+1

• Switch to firstWhere(orElse) for compatibility with the SDK dev.45

0.2.0

• Removed locking between uses of the Resolver and added a mandatory reset call to indicate that a complete build is finished.

0.1.1

• Support the latest analyzer package.

0.1.0

• Initial release as a migration from code_transformers with a near-identical implementation.