dfx generate is not compiling the candid if the canister is not deployed #2733
ozwaldorf
started this conversation in
Feature Requests
Replies: 5 comments 1 reply
-
Part of SDK-693 |
Beta Was this translation helpful? Give feedback.
0 replies
-
@sesi200 Can this be added as a feature request? (To discussions) |
Beta Was this translation helpful? Give feedback.
1 reply
-
Can you use |
Beta Was this translation helpful? Give feedback.
0 replies
-
This will be partially resolved in #2988 |
Beta Was this translation helpful? Give feedback.
0 replies
-
This will be fully resolved in #3093 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, if you have a child canister that is in the project, but does not get deployed directly by dfx and rather a parent canister, you cannot generate the bindings. The generation only works after creating the canister id. A usual workaround is specifying the management or anonymous principal id in canister_ids.json, but as generate only reads the local ids and they are always ephemeral, it requires manual intervention any time dfx is reset.
I suggest removing the canister id requirements for dfx generate, and only rely on the candid file existing
Beta Was this translation helpful? Give feedback.
All reactions