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

<div class="setting-label">
  <h3>{{settingName}}</h3>
  {{#if defaultIsAvailable}}
    <a href onClick={{action "setDefaultValues"}}>{{setting.setDefaultValuesLabel}}</a>
  {{/if}}
</div>
<div class="setting-value">
  {{component componentName setting=setting value=buffered.value validationMessage=validationMessage preview=preview isSecret=isSecret allowAny=allowAny}}
</div>
{{#if dirty}}
  <div class="setting-controls">
    {{d-button class="ok" action=(action "update") icon="check"}}
    {{d-button class="cancel" action=(action "cancel") icon="times"}}
  </div>
{{else if setting.overridden}}
  {{#if setting.secret}}
    {{d-button action=(action "toggleSecret") icon="far-eye-slash"}}
  {{/if}}
  {{d-button class="btn-default undo" action=(action "resetDefault") icon="undo" label="admin.settings.reset"}}
{{/if}}
Support for `url_list` site setting. 2015-03-03 01:12:19 +08:00			`<div class="setting-label">`
DEV: enforces ember-template-lint: no-unbound (#9147) From ember-template-lint documentation (https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-unbound.md): ``` {{unbound}} is a legacy hold over from the days in which Ember's template engine was less performant. Its use today is vestigial, and it no longer offers performance benefits. It is also a poor practice to use it for rendering only the initial value of a property that may later change. ``` Co-Authored-By: Jarek Radosz <jradosz@gmail.com> 2020-03-09 22:28:31 +08:00			`<h3>{{settingName}}</h3>`
FEATURE: ability to add all active components to theme (#8447) * FEATURE: ability to add all active components to theme * FIX: add a component to all themes takes only active ones * FIX: move select components/themes to top * FIX: improve defaultIsAvailable * FIX: Add filter(Boolean) and remove btn class 2019-12-04 14:13:41 +08:00			`{{#if defaultIsAvailable}}`
DEV: enforces no-invalid-interactive linting rule (#8907) 2020-02-11 22:55:16 +08:00			`<a href onClick={{action "setDefaultValues"}}>{{setting.setDefaultValuesLabel}}</a>`
FEATURE: Ability to add components to all themes (#8404) * FEATURE: Ability to add components to all themes This is the first and functional step from that topic https://dev.discourse.org/t/adding-a-theme-component-is-too-much-work/15398/16 The idea here is that when a new component is added, the user can easily assign it to all themes (parents). To achieve that, I needed to change a site-setting component to accept `setDefaultValues` action and `setDefaultValuesLabel` translated label. Also, I needed to add `allowAny` option to disable that for theme selector. I also refactored backend to accept both parent and child ids with one method to avoid duplication (Renamed `add_child_theme!` to more general `add_relative_theme!`) * FIX: Improvement after code review * FIX: Improvement after code review2 * FIX: use mapBy and filterBy directly 2019-11-28 13:19:01 +08:00			`{{/if}}`
Support for `url_list` site setting. 2015-03-03 01:12:19 +08:00			`</div>`
			`<div class="setting-value">`
FEATURE: Ability to add components to all themes (#8404) * FEATURE: Ability to add components to all themes This is the first and functional step from that topic https://dev.discourse.org/t/adding-a-theme-component-is-too-much-work/15398/16 The idea here is that when a new component is added, the user can easily assign it to all themes (parents). To achieve that, I needed to change a site-setting component to accept `setDefaultValues` action and `setDefaultValuesLabel` translated label. Also, I needed to add `allowAny` option to disable that for theme selector. I also refactored backend to accept both parent and child ids with one method to avoid duplication (Renamed `add_child_theme!` to more general `add_relative_theme!`) * FIX: Improvement after code review * FIX: Improvement after code review2 * FIX: use mapBy and filterBy directly 2019-11-28 13:19:01 +08:00			`{{component componentName setting=setting value=buffered.value validationMessage=validationMessage preview=preview isSecret=isSecret allowAny=allowAny}}`
Support for `url_list` site setting. 2015-03-03 01:12:19 +08:00			`</div>`
			`{{#if dirty}}`
			`<div class="setting-controls">`
FIX: default user preferenced categories are not updating in admin site setting UI. 2019-10-31 08:15:57 +08:00			`{{d-button class="ok" action=(action "update") icon="check"}}`
DEV: upgrades from Ember 2.13 to Ember 3.5.1 (#6808) Co-Authored-By: Bianca Nenciu <nbianca@users.noreply.github.com> Co-Authored-By: David Taylor <david@taylorhq.com> 2019-01-10 18:06:01 +08:00			`{{d-button class="cancel" action=(action "cancel") icon="times"}}`
Support for `url_list` site setting. 2015-03-03 01:12:19 +08:00			`</div>`
FIX: Allow HTML in site setting descriptions. 2015-05-28 23:34:44 +08:00			`{{else if setting.overridden}}`
FEATURE: improve handling of site setting secrets 2018-06-02 21:57:52 +08:00			`{{#if setting.secret}}`
icons deprecations fixes (#6920) 2019-01-22 19:02:02 +08:00			`{{d-button action=(action "toggleSecret") icon="far-eye-slash"}}`
FEATURE: improve handling of site setting secrets 2018-06-02 21:57:52 +08:00			`{{/if}}`
DEV: upgrades from Ember 2.13 to Ember 3.5.1 (#6808) Co-Authored-By: Bianca Nenciu <nbianca@users.noreply.github.com> Co-Authored-By: David Taylor <david@taylorhq.com> 2019-01-10 18:06:01 +08:00			`{{d-button class="btn-default undo" action=(action "resetDefault") icon="undo" label="admin.settings.reset"}}`
Support for `url_list` site setting. 2015-03-03 01:12:19 +08:00			`{{/if}}`