discourse/app/assets/javascripts/admin/templates/components/site-settings/enum.hbs

{{combo-box
  content=setting.validValues
  value=value
  onChange=(action (mut value))
  valueProperty=setting.computedValueProperty
  nameProperty=setting.computedNameProperty
  options=(hash
    castInteger=true
    allowAny=setting.allowsNone
  )
}}

{{preview}}

{{setting-validation-message message=validationMessage}}

<div class="desc">
  {{html-safe setting.description}}
</div>
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			`{{combo-box`
			`content=setting.validValues`
			`value=value`
			`onChange=(action (mut value))`
FIX: makes setting-object capable of defining value/name properties itself (#9003) 2020-02-19 10:01:21 +01:00			`valueProperty=setting.computedValueProperty`
			`nameProperty=setting.computedNameProperty`
FIX: brings back castInteger as a safer migration path for sk2 (#8966) 2020-02-14 10:00:40 +01:00			`options=(hash`
			`castInteger=true`
			`allowAny=setting.allowsNone`
			`)`
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			`}}`

Support for `url_list` site setting. 2015-03-02 12:12:19 -05:00			`{{preview}}`
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
Support for `url_list` site setting. 2015-03-02 12:12:19 -05:00			`{{setting-validation-message message=validationMessage}}`
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
DEV: enforces double quotes ember-template-lint (#9416) 2020-04-14 08:18:49 +02:00			`<div class="desc">`
DEV: enforces ember-template-lint: no-triple-curlies (#9165) This pr replaces `{{{ }}}` usage by a {{html-safe}} helper. While it doesn't solve the underlying issue, it gives us a path forward without risking breaking too much existing behavior. Also introduces an htmlSafe computed macro: ``` import { htmlSafe } from "discourse/lib/computed"; htmlDescription: htmlSafe("description") ``` Overtime {{html-safe}} usage should be removed and moved to components properties or specialized components/helpers. 2020-03-11 09:23:10 +01:00			`{{html-safe setting.description}}`
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			`</div>`