feat: Candid assist

[chenyan-dfinity]

Description

Ask for user input when candid argument is not provided. A nice side effect is that dfx deploy now works with multiple canisters with init args (we cannot use --argument flag when multiple canisters require init args)

How Has This Been Tested?

e2e test

Checklist:

• The title of this PR complies with Conventional Commits.
• I have edited the CHANGELOG accordingly.
• I have made corresponding changes to the documentation.

[adamspofford-dfinity]

Not easy to write e2e test, because it's only activated when used in terminal.

DFX has a number of interactive tests in Expect format, in e2e/assets/expect_scripts. See here for an example, may require updating this line.

[ericswanson-dfinity]

This happens when I run dfx new hello && cd hello && dfx deploy:

Installing code for canister hello_backend, with canister ID by6od-j4aaa-aaaaa-qaadq-cai
✔ Do you want to enter an optional value? · yes
  Enter a value for AssetCanisterArgs : variant { Upgrade : UpgradeArgs; Init : InitArgs }
  ✔ Select a variant · Init
    Enter a value for InitArgs : record {}
Sending the following argument:
(opt variant { Init = record {} })

Do you want to send this message? [y/N]

Expected behavior: deploying the default project doesn't block asking for any parameters.

(Also: it's prompting for the frontend canister, not the backend canister, but there's no indication of that at the "Do you want to enter an optional value?" prompt.)

[chenyan-dfinity]

Should be good now. I move the install prompts at the top. It also helps with other warning messages. Restored the behavior of not asking for arguments when all types are optional.

[ericswanson-dfinity]

Can we have one of these for deploy and install as well?

Here is the output I see when deploying to a canister declared as actor class c(p: { x: Nat; y: Int;}) :

Installing canisters...
Installing code for canister dd_backend, with canister ID bkyz2-fmaaa-aaaaa-qaaaq-cai
Enter field x : nat
  ✔ Enter a nat · 6
Enter field y : int
  ✔ Enter an int · 8
Sending the following argument:
(record { x = 6 : nat; y = 8 : int })

Do you want to send this message? [y/N]

Suggested wording:

Installing canisters...
Installing code for canister dd_backend, with canister ID bkyz2-fmaaa-aaaaa-qaaaq-cai

Canister dd_backend requires an initialization argument.
Enter field x : nat
  ✔ Enter a nat · 6
Enter field y : int
  ✔ Enter an int · 8

Initialization argument for dd_backend will be:
(record { x = 6 : nat; y = 8 : int })

Do you want to initialize canister dd_backend with this argument? [y/N]

[chenyan-dfinity]

Done

[ericswanson-dfinity]

Here's what I see now, when deploying a canister with declaration actor class c(x: Principal) {

Installing code for canister dd_backend, with canister ID bkyz2-fmaaa-aaaaa-qaaaq-cai
This canister requires the following initialization argument.
Auto-completions: alice, anonymous, bob, dd_backend, dd_frontend, default, mainnet
? Enter a principal › 

Note "This canister requires the following initialization argument." but no following description of the argument. The term "requires the following initialization argument" would have to refer to a "following" description of that argument. It can't be used to refer only to the upcoming prompt for that argument.

[chenyan-dfinity]

Changed back to "This canister requires an initialization argument."

[ericswanson-dfinity]

This set_completion call overwrites the completions, which makes it so anonymous doesn't show up in the list of autocompletion principals. Is that intended?

[chenyan-dfinity]

It's intended. We probably need to add anonymous manually in the identity export.