Add the possibility to prefill the answer about huh

[maaslalani]

I think the correct solution here would be to take the union of the two defaults. In this case all three would be selected as lettuce is in the toppings and the other two are selected.

Really good call on catching this intended behaviour btw! Thank you so much!

[maaslalani]

Hey @Iilun, this is possible if you set the variable to the default value you want:

value := "default value"

huh.NewInput().Value(&value).Run()

The field will be pre-filled with the value ("default value")

[vitor-mariano]

@maaslalani All the fields can be prefilled with Value(&value), except Select and MultiSelect. I know I can achieve the same behavior with huh.NewOption(...).Selected(true), but not with huh.NewOptions. Is this on purpose? Using Value(&value) would be interesting in scenarios when editing existing data and keeping consistency with other field types.

If this behavior is not intended, I'd love to open a PR fixing it!

[maaslalani]

Hey @vitor-mariano, yes we'd love to accept a PR that inspects the default value of select and multi-select and pre-selects the values.

toppings := []string{"lettuce", "tomatoes"}

huh.NewMultiSelect().Options(huh.NewOptions("lettuce", "tomatoes", "cheese")).Value(&toppings).Run()
// first two should be selected

[vitor-mariano]

@maaslalani before moving forward with the fix, what should happen if I have both value and Selected(true)? Eg

huh.NewMultiSelect().
    Options(
        huh.NewOption("lettuce", "lettuce"),
        huh.NewOption("tomatoes", "tomatoes").Selected(true),
        huh.NewOption("cheese", "cheese").Selected(true),
    ).
    Value(&toppings).
    Run()