Multi-select with grouped values

[awgymer]

Is it possible to have a multiple choice question where selecting a particular answer would "auto-select" other options?

So e.g.:

extra_tools:                                                                                                                                
    type: str                                      
    multiselect: true                                                                                                                         
    default: []                                                                          
    choices: 
        uv: uv
        mytool: [uv, mytool]
        othertool: [uv, othertool]

This is a very small example, but the idea is that you could stop the user having to individually select options which are required for other options to also work in your final template.

I suspect this is probably only possible if such a thing is supported by questionary.

[sisp]

This isn't possible at the moment. If it was, what would happen if a user selected mytool, which triggered an auto-selection of uv, and then the user deselected uv? Should this be prevented, and if so, how would this constraint be communicated? Or should this be possible while showing an error message?

Ideally questionary should support this feature, so we don't need to find workarounds.

Meanwhile, this might be an admittedly hacky and suboptimal solution:

extra_tools:
  type: str
  multiselect: true
  default: []
  choices:
    uv: uv
    mytool: mytool
    othertool: othertool
  validator: >-
    {%- set errors = [] -%}
    {%- for tool, requires in {
      'uv': [],
      'mytool': ['uv'],
      'othertool': ['uv']
    } | items -%}
      {%- if tool in extra_tools -%}
        {%- for required in requires -%}
          {%- if required not in extra_tools -%}
            {%- set _ = errors.append(tool ~ ' requires ' ~ required) -%}
          {%- endif -%}
        {%- endfor -%}
      {%- endif -%}
    {%- endfor -%}
    {{- errors | join(' & ') -}}

[awgymer]

Ah ok you've done it via a validator.

My workaround for now was to have the choices be yaml and have labels to lists of the dependencies and then have a computed value made by flattening and deduping the selected lists.

In this scenario users are not able to "deselect" a required dependency of any of their selections, so there is that limitation.