-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Make asset consumption more explicit #16612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Removed Pub-Build label. |
Removed Priority-Unassigned label. |
From our discussion yesterday, the current plan is that we'll add a method like: consumeInput(AssetId id) to Transform. Transformers can call that to explicitly prevent that asset from being forwarded. In addition, we'll change the default behavior so that a primary input is not automatically consumed. As far as we know, changing that default won't break any existing transformers because most of those output an asset on top of the primary input, which still effectively consumes it since it gets overwritten. |
Issue #14554 has been merged into this issue. |
Changed the title to: "Make asset consumption more explicit". |
After some discussion (see https://code.google.com/p/dart/issues/detail?id=14554#c5 for details), we've decided not to expose a general [consumeInput] function. Instead, we'll add a [consumePrimaryInput] function. |
r33134 adds support for passing assets through a transformer by default. |
r33557 adds the ability for transformers to explicitly consume their primary inputs. Added Fixed label. |
This issue has been moved to dart-lang/pub#847. |
Scenario: I have 10 pngs files in assets.
I'd like to generate a single png sprite, with a new file name, and not include the source images in output
The text was updated successfully, but these errors were encountered: