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

<input
  {{on "input" (with-event-value (fn (mut this.value)))}}
  type="number"
  value={{this.value}}
  min={{if this.setting.min this.setting.min null}}
  max={{if this.setting.max this.setting.max null}}
  class="input-setting-integer"
/>

<SettingValidationMessage @message={{this.validationMessage}} />
<div class="desc">{{html-safe this.setting.description}}</div>
FIX: Deprecate NumberField, use <input> instead (#25434) * Revert "FEATURE: Use native number fields for integer inputs (#24984)" This reverts commit 8fce890eadacf5387e12f48db3ffe82211a1fddc. * FIX: Deprecate NumberField, use <input> instead This reverts #24984 as it introduced regressions (behavioral and visual) and instead it deprecates the NumberField component and replaces its uses in core with native `<input>` elements. 2024-01-27 00:56:07 +08:00			`<input`
DEV: Introduce a helper for handling events (#25433) Instead of ```hbs {{on "input" (action this.foo value="target.value")}} {{on "input" (action (mut this.bar) value="target.value")}} ``` you can use: ```hbs {{on "input" (with-event-value this.foo)}} {{on "input" (with-event-value (fn (mut this.bar)))}} ``` or in gjs: ```gjs import { fn } from "@ember/helper"; import { on } from "@ember/modifier"; import withEventValue from "discourse/helpers/with-event-value"; … {{on "input" (withEventValue (fn (mut this.bar)))}} ``` 2024-02-28 21:00:53 +08:00			`{{on "input" (with-event-value (fn (mut this.value)))}}`
FIX: Site-setting integer input type (#25485) Regressed in f2e1363f6727ef837e957911f258ac436e09708e 2024-01-31 03:25:48 +08:00			`type="number"`
FIX: Deprecate NumberField, use <input> instead (#25434) * Revert "FEATURE: Use native number fields for integer inputs (#24984)" This reverts commit 8fce890eadacf5387e12f48db3ffe82211a1fddc. * FIX: Deprecate NumberField, use <input> instead This reverts #24984 as it introduced regressions (behavioral and visual) and instead it deprecates the NumberField component and replaces its uses in core with native `<input>` elements. 2024-01-27 00:56:07 +08:00			`value={{this.value}}`
			`min={{if this.setting.min this.setting.min null}}`
			`max={{if this.setting.max this.setting.max null}}`
			`class="input-setting-integer"`
FIX: min/max not passed to NumberField for site settings (#24402) When we started using NumberField for integer site settings in e113eff6634c9b398b0541ea6a0d1626f6732dcc, we did not end up passing down a min/max value for the integer to the field, which meant that for some fields where negative numbers were allowed we were not accepting that as valid input. This commit passes down the min/max options from the server for integer settings then in turn passes them down to NumberField. c.f. https://meta.discourse.org/t/delete-user-self-max-post-count-not-accepting-1-to-disable/285162 2023-11-16 10:37:05 +08:00			`/>`
DEV: Sanitize integer site settings in front- and back-end (#23816) Currently, if you set an integer site setting in the admin interface and include thousands separators, you will silently configure the wrong value. This PR replaces TextField inputs for integer site settings with NumberField. It also cleans the numeric input of any non-digits in the backend in case any separators make it through. 2023-10-07 01:21:01 +08:00
			`<SettingValidationMessage @message={{this.validationMessage}} />`
			`<div class="desc">{{html-safe this.setting.description}}</div>`