specify assets that are for development only

[eukreign]

It would be useful to specify some assets that should be loaded only during development and ignored when doing a release build.

I'm proposing adding a dev_assets option to flutter.yml to mimic the similar concept of dev_dependencies in the standard Dart pubspec.yaml.

This feature is in someway related #4014 in that you need a way to know in your code that dev_assets are available to use.

[eseidelGoogle]

Do Android or iOS OEM build systems have equivalents we should either use or match here?

Incidentally Google internal flutter users can do something like this because they use bazel, and the flutter_application bazel rule takes a list of assets (instead of getting them from flutter.yaml). We have a very simple build system built into the flutter tool on top of flutter.yaml, sounds like this is asking for something a bit more sophisticated.

[photex]

Are there any plans to bring the internal bazel rules for flutter out into the open source bazel?

We are likely going to pass over flutter because we spent a lot of effort setting up that "one true build" with bazel.

[Remigius2011]

see also: https://stackoverflow.com/a/75056022/3639856

[eximius313]

Imagine having local configuration file with credentials used only by devs.
In production this file is delivered by server environment, so the local file should not be included in the build.

[tcannon-disney]

We have a use case where we are a published package but would like to denote that some of the assets are for testing usage only. I feel like a dev_assets: section would be ideal for this kind of usage.

[drown0315]

We have a use case where we are a published package but would like to denote that some of the assets are for testing usage only. I feel like a dev_assets: section would be ideal for this kind of usage.我们有一个用例，其中我们是已发布的包，但想指出某些资产仅用于测试使用。我觉得 dev_assets: 部分非常适合这种用法。

I faced the same scenario: I wrote a general widget package and made a golden test on a widget that required some images.