What's the proper way to pass a list to a solid in a preset? I have solid

datasplit_y

with an argument

id_cols

that takes a list of strings. All of the below have failed: 1

datasplit_y:
    inputs:
      id_cols: 
        - user_id
        - program_day

2

datasplit_y:
    inputs:
      id_cols:
        value:
          - user_id
          - program_day

3

datasplit_y:
    inputs:
      id_cols: [user_id, program_day]

4

datasplit_y:
    inputs:
      id_cols: ['user_id', 'program_day']

5

datasplit_y:
    inputs:
      id_cols: 
        value: ['user_id', 'program_day']

6

datasplit_y:
    inputs:
      id_cols: 
        value: ['user_id', 'program_day']

7

datasplit_y:
    inputs:
      id_cols: 
        value: "['user_id', 'program_day']"

8

datasplit_y:
    inputs:
      id_cols: 
        value: "[user_id, program_day]"

Clearly I'm throwing hail-marys at this point. Any advice?

in yaml? I belive it looks like

solids:
  solid_name:
    inputs:
      input_name:
        - value
        - value

I've tried that form, and it is typed as

List

. Does it matter that list is from the core library's

typing

and not from Dagster?

that should be fine

When it's in the form you suggested I get error:

Value selector for type a path root:solids:datasplit_y:inputs:id_cols[0] must be a dict

and then the same error but with

id_cols[1]

ideas:

solids:
  solid_name:
    inputs:
      input_name: [x, y, z]

solids:
  solid_name:
    inputs:
      input_name:
        - value: actual_value
        - value: actual_other_value

solids:
  solid_name:
    inputs:
      input_name:
        - value: actual_value
        - value: actual_other_value

Appears to have worked! Thanks @alex

ya its a bit annoying to have to key

value

but thats how we distinguish between the direct value vs passing like a file path to go read the value from

yep, makes sense

whats the inner type out of curiosity ?

just strings

kk i think its a bug that we don’t handle the direct values as the list - we make that work in the singular case so i think its just an issue in the list handler

this has annoyed me enough that I parse lists of strings from a single string value inside the solid