Meta issue for the difficulty of using assets with Flutter #27802
Labels
a: assets
Packaging, accessing, or using assets
customer: crowd
Affects or could affect many people, though not necessarily a specific customer.
P2
Important issues not at the top of the work list
team-tool
Owned by Flutter Tool team
tool
Affects the "flutter" command-line tool. See also t: labels.
triaged-tool
Triaged by Flutter Tool team
Projects
I wanted to try and highlight how several outstanding issues related to assets really hurt productivity:
Including all the files in a directory is only supported for the current package:
Related: Does not includes all the assets under a folder from external package #22944
Flutter packages (i.e. not apps) cannot declare their own assets:
... will result in runtime asset errors. See above issue for why this is difficult to workaround.
Related: Flutter packages containing assets are hard to manage and not intuitive #22921
Asset inclusion only works by individual file or individual folder
Related: Support wildcard/globs in
flutter: assets:
YAML #27801Assets added to a directory are not picked up during hot reload/restart:
... leading the need of killing and restarting the app from scratch when working with assets.
Related: Trigger assets scan again if a file is added/removed to scanned folder #18896
Assets are not usable in (non-driver) tests:
... meaning that testing packages that provide assets is very difficult.
Related: Make assets available during tests. #12999
The text was updated successfully, but these errors were encountered: