You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: