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

<ComboBox
  @content={{this.setting.validValues}}
  @value={{this.value}}
  @onChange={{fn (mut this.value)}}
  @valueProperty={{this.setting.computedValueProperty}}
  @nameProperty={{this.setting.computedNameProperty}}
  @options={{hash castInteger=true allowAny=this.setting.allowsNone}}
/>

{{this.preview}}
No implicit this codemod (#17235) * Run no-implicit-this codemod for app templates * Run tagless-ember-components-codemod for plugins * Turn on no-implicit-this lint 2022-07-05 10:41:31 -07:00			`<ComboBox`
			`@content={{this.setting.validValues}}`
			`@value={{this.value}}`
DEV: Use fn+mut instead of action+mut (#26057) One step closer to removing all `action` helper usage 2024-03-06 18:05:03 +01:00			`@onChange={{fn (mut this.value)}}`
No implicit this codemod (#17235) * Run no-implicit-this codemod for app templates * Run tagless-ember-components-codemod for plugins * Turn on no-implicit-this lint 2022-07-05 10:41:31 -07:00			`@valueProperty={{this.setting.computedValueProperty}}`
			`@nameProperty={{this.setting.computedNameProperty}}`
			`@options={{hash castInteger=true allowAny=this.setting.allowsNone}}`
DEV: Run angle-brackets codemod (#17286) Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com> 2022-06-30 12:30:50 +02:00			`/>`
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
FIX: Make cancel and reset buttons work for `file_size_restriction` settings (#28347) This commit fixes a number of bugs in `file_size_restriction` settings and does a little of refactoring to reduce duplicated code in site setting types (the refactoring is necessary to fix one of the bugs). The bugs in `file_size_restriction` settings that are fixed in this commit: 1. Save/cancel buttons next to a `file_size_restriction` setting are shown upon navigating to the settings page without changes being made to the setting 2. Cancel button that discards changes made to the setting doesn't work 3. Reset button that resets the setting to its default doesn't work 4. Validation error message isn't cleared when resetting/cancelling changes To repro those bugs, navigate to `/admin/site_settings/category/files` and observe the top 2 settings in the page (`max image size kb` and `max attachment size kb`). Internal topic: t/134726. 2024-08-15 19:38:47 +03:00			`{{this.preview}}`