mirror of
https://github.com/discourse/discourse.git
synced 2025-02-18 04:22:47 +08:00
![]() * 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 |
||
---|---|---|
.. | ||
admin-dashboard.js.es6 | ||
admin-user.js.es6 | ||
api-key.js.es6 | ||
backup-status.js.es6 | ||
backup.js.es6 | ||
color-scheme-color.js.es6 | ||
color-scheme.js.es6 | ||
email-log.js.es6 | ||
email-preview.js.es6 | ||
email-settings.js.es6 | ||
email-style.js.es6 | ||
email-template.js.es6 | ||
flag-type.js.es6 | ||
incoming-email.js.es6 | ||
permalink.js.es6 | ||
report.js.es6 | ||
screened-email.js.es6 | ||
screened-ip-address.js.es6 | ||
screened-url.js.es6 | ||
site-setting.js.es6 | ||
site-text.js.es6 | ||
staff-action-log.js.es6 | ||
theme-settings.js.es6 | ||
theme.js.es6 | ||
tl3-requirements.js.es6 | ||
user-field.js.es6 | ||
version-check.js.es6 | ||
watched-word.js.es6 | ||
web-hook.js.es6 |