Agreed!

I think we should do it without changing anything in the provider and should convert any parameter with more than 4 options to a drop-down

@matifali I think there should be an option in the provider to allow the user to choose.

@timquinlan I agree. so it can probably work like this

data "coder_paramter" "options" {
	name         = "options"
	display_name = "Options to choose"
	description  = "Choose 1 option"
	default      = "option1"
	style|type   = "bullets|dropdown"  # defaults to bullets to keep up the old behavior 
	option {
		name  = "foo"
		value = "option1"
	}
	option {
		name  = "bar"
		value = "option2"	
	}
	...
	option {
		name  = "bar"
		value = "option10"	
	}
}

cc: @timquinlan

@sreya, are we planning to do it automatically, or want to give the user an option to choose the style? In the later case, we need to update the provider first. I personally prefer to handle in frontend depending on the number of option blocks.

Yeah that's what we're planning on doing. No provider changes. cc @aslilac

I thought we decided to punt on this for now

Oh whoops you're right. We can maybe circle back around to this on the spillover week for the sprint.

Hi, I was about to file this as a feature request but I'll just bring this issue back up to attention instead. 😃

I think it would be nice if the dropdown field would also allow entering text to filter choices. An option field in my template has 20+ options and it's not a great UX to parse that list.

(more below when scrolling)

I agree. A drop-down list with a search bar to filter options as we type would be great UX.

I would also greatly appreciate this. I would also go so far as to suggest an optional typeahead input as we have many different VM image names that would be handy to be able to just start typing and the list would update to only those that include the substring.

We should add this if it's an easy lift or handle this case as part of #5540 and #11275

I would also greatly appreciate this. I would also go so far as to suggest an optional typeahead input as we have many different VM image names that would be handy to be able to just start typing and the list would update to only those that include the substring.

This could be a separate request to allow search through coder_parameter options.