v4.1.0

Features

Cache location

You're now able to set a custom cache location by setting catalyst_builder: { cacheDir: 'a/cache/path' } property in the pubspec.yaml

Take a look in pubspec.yaml for an example.

Internal

• The CacheHelper is no longer static.

v4.0.0

This major update has breaking changes.
Check the UPGRADE.md for guidance.

Features

Caching system

This release contains a new caching system for intermediates. Those are stored in a .catalyst_builder_cache directory.
Don't forget to exclude this from the VCS.

Changes

Dependency updates

• build_runner_core: Removed

Breaking Changes:

Dart SDK

Bump the minimum Dart SDK version to 3.5.0

Dependency updates

• dart_style: ^2.0.1 => ^3.0.1
• analyzer: '>=5.2.0 <7.0.0' => '>=5.2.0 <8.0.0'

Annotations

Removed the deprecated @Parameter annotation. Use @Inject instead.

Build customization

Moved the providerClassName and includePackageDependencies option to the @GenerateServiceProvider annotation

v3.6.0

Fixed updating the generated provider file

In this release we hopefully fixed the old problem with outdated *.catalyst_builder.g.dart files.

Cause

The ServiceProviderBuilder did not emit an updated version since the @GenerateServiceProvider annotation
doesn't exist in the most files.

Solution

We added a new generatedProviderFile option to the preflightBuilder configuration. You need to put the relative path
to the generated provider file (*.catalyst_builder.g.dart) in this option.
The PreflightBuilder will automatically delete the file if it exists. This lead to a full regeneration of the service
provider file. 🙌

v3.5.2

Fix downgrade error

In version 5.0.0 of the analyzer Package was DartType.element removed.
It was added again in 5.2.0 so we updated the version constraint to >=5.2.0 <7.0.0 to fix that downgrade error.

v3.5.1

Singleton instances on enhanced providers

Previously each ServiceProvider had a map of service instances. If a singleton was created, the provider stored the
instance in the map and returned the instance the next time it is requested.

If you're working with enhanced providers (ServiceProvider.enhance), the singletons created in the EnhancedProvider
wasn't stored in the root provider which causes that a singleton will be created again if it's resolved in the root
provider.

To solve this problem, the instances of the map is now a reference to the original instances map of the parent provider.

Dependency updates

Moved the lints to dev_dependencies and set the version constraint to any

v3.5.0

Updated the version constraint of the analyzer package.

v3.4.0

Features:

• Added an example for working with relative dependencies. PR#19

Changes:

• The preflight builder will no more emit empty files. This should increase the build performance. PR#18

v3.3.1

Fixes:

• Fixed the enhance method. PR#16

v3.3.0

Features:

• Added stricter rules to analysis_options.yaml
  • Added type castings to the generated service provider.

v3.2.3

Fixes:

• Fixed the enhance method and overtake the expose map and the known services map.