discourse/app/assets/javascripts/wizard/templates/components/wizard-field-dropdown.hbs

{{component
  componentName
  class=fieldClass
  value=field.value
  content=field.choices
  nameProperty="label"
  tabindex="9"
  onChange=(action "onChangeValue")
  options=(hash
    translatedNone=false
  )
}}
UX: Add Styling step to wizard (#14132) Refactors three wizard steps (colors, fonts, homepage style) into one new step called Styling. 2021-08-25 17:10:12 -04:00			`{{component`
			`componentName`
DEV: select-kit 2 (#7998) This new iteration of select-kit focuses on following best principales and disallowing mutations inside select-kit components. A best effort has been made to avoid breaking changes, however if you content was a flat array, eg: ["foo", "bar"] You will need to set valueProperty=null and nameProperty=null on the component. Also almost every component should have an `onChange` handler now to decide what to do with the updated data. select-kit will not mutate your data by itself anymore 2020-02-03 14:22:14 +01:00			`class=fieldClass`
			`value=field.value`
			`content=field.choices`
			`nameProperty="label"`
			`tabindex="9"`
UX: Add Styling step to wizard (#14132) Refactors three wizard steps (colors, fonts, homepage style) into one new step called Styling. 2021-08-25 17:10:12 -04:00			`onChange=(action "onChangeValue")`
			`options=(hash`
			`translatedNone=false`
			`)`
DEV: select-kit 2 (#7998) This new iteration of select-kit focuses on following best principales and disallowing mutations inside select-kit components. A best effort has been made to avoid breaking changes, however if you content was a flat array, eg: ["foo", "bar"] You will need to set valueProperty=null and nameProperty=null on the component. Also almost every component should have an `onChange` handler now to decide what to do with the updated data. select-kit will not mutate your data by itself anymore 2020-02-03 14:22:14 +01:00			`}}`