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
Should we export @dfinity/candid IDL, or should we make it a peer dependency??? The versions must be exactly the same, but a peer dependency could probably resolve this
query
update
dynamic method name gathering
All canister methods
init
pre upgrade
post upgrade
inspect message
heartbeat
cross-canister calls (just do call or callRaw style...probably call and callRaw are similar)
composite queries
manual
guard functions
callRaw
make sure context (this) is set correctly on all of the decorators
make sure all canister methods handle async appropriately
make sure only one class can be the true cannonical canister method class...maybe we need to extend from Canister then?
rename canister_syntax in package.json names to functional_syntax
get rid of azle/canisters
All stable APIs should be imported directly from azle
All experimental APIs should be imported directly from azle/experimental
ic and canisters need to be in experimental
Explore IDL.Type everywhere, we might be able to get some good type checking
check if the new native decorators can change param and return types of their functions
make sure there are only two possible imports, experimental and azle. Canisters should be under experimental, like icrc, management canister...though maybe we should make a way for people to abstract
automatically generate the candid and update all of the examples: change to automatic, remove candid line
can guard functions be async?
Update esbuild to the lastest version so we we can rid of experimental decorators
add vanilla js test back in and make sure it works with new decorators
Other things to consider
remove azle/canisters
make sure examples are getting types with generated files from candid files
generate candid types for management, ledger, etc instead of maintaining those types
Other things to consider
The text was updated successfully, but these errors were encountered: