mirror of
https://github.com/discourse/discourse.git
synced 2024-11-24 18:46:50 +08:00
b120728999
* 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 | ||
admin-login | ||
discourse | ||
discourse-common | ||
docs | ||
ember-addons | ||
locales | ||
pretty-text | ||
select-kit | ||
wizard | ||
activate-account.js.no-module.es6 | ||
admin.js.erb | ||
application.js | ||
auto-redirect.js.no-module.es6 | ||
deprecated.js | ||
discourse-loader.js | ||
discourse-objects.js | ||
discourse.js.es6 | ||
embed-application.js.no-module.es6 | ||
ember_include.js.erb | ||
ember_jquery.js | ||
ember-shim.js | ||
env.js | ||
google-tag-manager.js.no-module.es6 | ||
google-universal-analytics.js.no-module.es6 | ||
main_include_admin.js | ||
markdown-it-bundle.js | ||
onpopstate-handler.js.no-module.es6 | ||
polyfills.js | ||
preload-application-data.js.no-module.es6 | ||
preload-store.js.es6 | ||
pretty-text-bundle.js | ||
print-page.js | ||
service-worker.js.erb | ||
set-prototype-polyfill.js | ||
template_include.js.erb | ||
vendor.js | ||
wizard-application.js | ||
wizard-start.js.no-module.es6 | ||
wizard-vendor.js |