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

<NumberField
  @value={{this.value}}
  @classNames="input-setting-integer"
  @min={{(if this.setting.min this.setting.min null)}}
  @max={{(if this.setting.max this.setting.max null)}}
/>

<SettingValidationMessage @message={{this.validationMessage}} />
<div class="desc">{{html-safe this.setting.description}}</div>
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			`<NumberField`
			`@value={{this.value}}`
			`@classNames="input-setting-integer"`
			`@min={{(if this.setting.min this.setting.min null)}}`
			`@max={{(if this.setting.max this.setting.max null)}}`
			`/>`
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>`