Asset canisters are common enough that it would be nice to have explicit support for them.
The canister itself could be deployed with the existing provider, especially if "asset canister" is going to become a library, so any canister can have an asset canister interface plus additional backend capability. I'm wary of suggesting that we add assets as an optional parameter to all canisters. Do you know of a more modular way of doing this?
Asset canisters are common enough that it would be nice to have explicit support for them.
The canister itself could be deployed with the existing provider, especially if "asset canister" is going to become a library, so any canister can have an asset canister interface plus additional backend capability. I'm wary of suggesting that we add assets as an optional parameter to all canisters. Do you know of a more modular way of doing this?