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
Is your feature request related to a problem? Please describe.
If a canister is written with a CDK that is not Azle, then Azle developers will have to manually implement the TypeScript types necessary to interact with those canisters. Since most/all canisters written in Rust/Motoko will have Candid files available, automatically generating Azle TypeScript types from those files could save developers a lot of work.
Describe the solution you'd like
didc bind path_to_candid.did -t azle should produce TypeScript types usable in canisters written in Azle.
Describe alternatives you've considered
Developers can implement the types themselves, or some standalone tool could generate these types.
The text was updated successfully, but these errors were encountered:
Azle's new syntax that will be taken to 1.0 how uses the IDL objects generated by didc. We still need this issue resolved to take full advantage of those: #569
Is your feature request related to a problem? Please describe.
If a canister is written with a CDK that is not Azle, then Azle developers will have to manually implement the TypeScript types necessary to interact with those canisters. Since most/all canisters written in Rust/Motoko will have Candid files available, automatically generating Azle TypeScript types from those files could save developers a lot of work.
Describe the solution you'd like
didc bind path_to_candid.did -t azle
should produce TypeScript types usable in canisters written in Azle.Describe alternatives you've considered
Developers can implement the types themselves, or some standalone tool could generate these types.
The text was updated successfully, but these errors were encountered: