discourse/app/assets/javascripts/admin/addon/components/inline-edit-checkbox.hbs

<label class="checkbox-label">
  <Input @type="checkbox" disabled={{this.disabled}} @checked={{this.buffer}} />
  {{i18n this.labelKey}}
</label>
{{#if this.changed}}
  <DButton
    @action={{action "apply"}}
    @class="btn-primary btn-small submit-edit"
    @icon="check"
  />
  <DButton
    @action={{action "cancel"}}
    @class="btn-small cancel-edit"
    @icon="times"
  />
{{/if}}
FEATURE: Native theme support This feature introduces the concept of themes. Themes are an evolution of site customizations. Themes introduce two very big conceptual changes: - A theme may include other "child themes", children can include grand children and so on. - A theme may specify a color scheme The change does away with the idea of "enabled" color schemes. It also adds a bunch of big niceties like - You can source a theme from a git repo - History for themes is much improved - You can only have a single enabled theme. Themes can be selected by users, if you opt for it. On a technical level this change comes with a whole bunch of goodies - All CSS is now compiled using a custom pipeline that uses libsass see /lib/stylesheet - There is a single pipeline for css compilation (in the past we used one for customizations and another one for the rest of the app - The stylesheet pipeline is now divorced of sprockets, there is no reliance on sprockets for CSS bundling - CSS is generated with source maps everywhere (including themes) this makes debugging much easier - Our "live reloader" is smarter and avoid a flash of unstyled content we run a file watcher in "puma" in dev so you no longer need to run rake autospec to watch for CSS changes 2017-04-12 10:52:52 -04:00			`<label class="checkbox-label">`
DEV: Update linting setup and fix issues (#17345) Re-lands #16119 and #17298 * Update eslint-config-discourse * Update linting workflow * Prettier-ignore stuff * Update template-lint config * Auto-fix template issues * Fix various template issues Mostly incorrect attributes and unused templates * Prettier js files * Fix template auto-fix regressions * Small css tweak Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com> 2022-07-06 10:37:54 +02:00			`<Input @type="checkbox" disabled={{this.disabled}} @checked={{this.buffer}} />`
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			`{{i18n this.labelKey}}`
FEATURE: Native theme support This feature introduces the concept of themes. Themes are an evolution of site customizations. Themes introduce two very big conceptual changes: - A theme may include other "child themes", children can include grand children and so on. - A theme may specify a color scheme The change does away with the idea of "enabled" color schemes. It also adds a bunch of big niceties like - You can source a theme from a git repo - History for themes is much improved - You can only have a single enabled theme. Themes can be selected by users, if you opt for it. On a technical level this change comes with a whole bunch of goodies - All CSS is now compiled using a custom pipeline that uses libsass see /lib/stylesheet - There is a single pipeline for css compilation (in the past we used one for customizations and another one for the rest of the app - The stylesheet pipeline is now divorced of sprockets, there is no reliance on sprockets for CSS bundling - CSS is generated with source maps everywhere (including themes) this makes debugging much easier - Our "live reloader" is smarter and avoid a flash of unstyled content we run a file watcher in "puma" in dev so you no longer need to run rake autospec to watch for CSS changes 2017-04-12 10:52:52 -04:00			`</label>`
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			`{{#if this.changed}}`
DEV: Run angle-brackets codemod (#17286) Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com> 2022-06-30 12:30:50 +02:00			`<DButton`
			`@action={{action "apply"}}`
			`@class="btn-primary btn-small submit-edit"`
			`@icon="check"`
			`/>`
			`<DButton`
			`@action={{action "cancel"}}`
			`@class="btn-small cancel-edit"`
			`@icon="times"`
DEV: Apply prettier to hbs files 2022-12-28 12:28:11 +00:00			`/>`
FEATURE: Native theme support This feature introduces the concept of themes. Themes are an evolution of site customizations. Themes introduce two very big conceptual changes: - A theme may include other "child themes", children can include grand children and so on. - A theme may specify a color scheme The change does away with the idea of "enabled" color schemes. It also adds a bunch of big niceties like - You can source a theme from a git repo - History for themes is much improved - You can only have a single enabled theme. Themes can be selected by users, if you opt for it. On a technical level this change comes with a whole bunch of goodies - All CSS is now compiled using a custom pipeline that uses libsass see /lib/stylesheet - There is a single pipeline for css compilation (in the past we used one for customizations and another one for the rest of the app - The stylesheet pipeline is now divorced of sprockets, there is no reliance on sprockets for CSS bundling - CSS is generated with source maps everywhere (including themes) this makes debugging much easier - Our "live reloader" is smarter and avoid a flash of unstyled content we run a file watcher in "puma" in dev so you no longer need to run rake autospec to watch for CSS changes 2017-04-12 10:52:52 -04:00			`{{/if}}`