Skip to content

Hive already initialized #59

@limonadev

Description

@limonadev

This library depends on the Hive package, and internally is calling await Hive.initFlutter(subDir);. However, an app could be already using Hive and having to initialize it in its own way (an app could be already calling await Hive.initFlutter(subDir);). Is it possible for this package to operate in its own Hive instance to avoid initialization conflicts or race conditions?

Also, is it possible for FastCachedImageConfig.init() to throw an exception? What would happen with the image loading in that case? As the package mentions, that method should not be called twice so if it fails there is option to retry?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions