When I run
dfx build it does generate the definition for the main actor (“Map”) but, does not generate the definition for the class actor (“Bucket”).
Is that a known issue? Or do I need in that particular case to implement something so that Candid also generates the types for the sub-canisters?
The Motoko code I implemented so far: deckdeckgo/studio/canisters/decks at feat/one-deck-one-canister · deckgo/deckdeckgo · GitHub
update: I can add my sub-actor in
dfx.json to generate the types but then, if I wish to deploy, it asks me to register a canister id in
canister_ids.json which I don’t want to, as these canisters should be generated on the fly.
So what I did, I add it to
dfx.json, generated the types and then removed the entry in
dfx.json to be able to deploy. Not sure if it is the expected behavior or is there a configuration flag that says such canister should not be listed in
canister_ids.json to not block the deployment?