discourse/app/assets/javascripts/admin/addon/components/theme-setting-editor.js

import SiteSettingComponent from "./site-setting";

export default class extends SiteSettingComponent {
  _save() {
    return this.setting.updateSetting(
      this.model.id,
      this.get("buffered.value")
    );
  }
}
DEV: Sort imports Automatically generated by `eslint --fix` to satisfy the updated configuration 2023-10-10 14:38:59 -04:00			`import SiteSettingComponent from "./site-setting";`
FEATURE: Theme settings (2) (#5611) Allows theme authors to specify custom theme settings for the theme. Centralizes the theme/site settings into a single construct 2018-03-04 19:04:23 -05:00
DEV: Remove layoutName references to site-settings component template 2023-02-13 05:53:15 -05:00			`export default class extends SiteSettingComponent {`
DEV: Refactor setting component save callback (#8261) * DEV: Refactor setting component save callback * refactor site-setting component around new callback * add callback to theme-translation component * remove the save callback altogether 2019-10-29 13:01:45 -04:00			`_save() {`
DEV: Allow typed objects theme settings to be saved via settings editor (#26100) Why this change? On the `/admin/customize/themes/<:id>` route, we allow admins to edit all settings via a settings editor. Prior to this change, trying to edit and save a typed objects theme settings will result in an error on the server. 2024-03-10 20:42:12 -04:00			`return this.setting.updateSetting(`
			`this.model.id,`
			`this.get("buffered.value")`
			`);`
DEV: Remove layoutName references to site-settings component template 2023-02-13 05:53:15 -05:00			`}`
			`}`