Releases: mintware-de/catalyst_builder
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
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