Skip to content

[native_assets_cli] Fallback asset types supportedAssetTypes #2154

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

Open
dcharkes opened this issue Apr 1, 2025 · 1 comment
Open

[native_assets_cli] Fallback asset types supportedAssetTypes #2154

dcharkes opened this issue Apr 1, 2025 · 1 comment

Comments

@dcharkes
Copy link
Collaborator

dcharkes commented Apr 1, 2025

Hook authors might want to use a certain asset type if available, and another one if the first one is not available.

For these it could be useful to have an input.config.supportedAssetTypes which signals with which input.config.buildAssetTypes the hook will be invoked besides the current invocation.

Edit: The SDKs could invoke the hooks for all asset types and based on asset-ids decide for one asset over another. However, the Dart code might make the JarAsset available under a different asset ID than the CodeAsset. (Or a JarAsset might not even have an asset ID.)

@mosuem
Copy link
Member

mosuem commented Apr 1, 2025

I think the SDKs should make that decision - the hooks should just build assets based on what the SDK is asking for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants