Repository navigation
specify assets that are for development only #5813
Description
Activity
- modified the milestone:
on Sep 12, 2016 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
fluttertool on top of flutter.yaml, sounds like this is asking for something a bit more sophisticated.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.
Reacted by Dimiter 'malkia' Stanev- modified the milestones: ,
on Jan 7, 2020 - modified the milestone:
on Jun 1, 2020 - removed this from the milestone
on Jun 16, 2020 - removed this from the milestone
on Jul 7, 2020 - modified the milestone:
on Jul 22, 2020 - removed this from the milestone
on Aug 17, 2020 - Reacted by Tsung-Han Yu
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.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.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.
It would be useful to specify some assets that should be loaded only during development and ignored when doing a
releasebuild.I'm proposing adding a
dev_assetsoption toflutter.ymlto mimic the similar concept ofdev_dependenciesin 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_assetsare available to use.