discourse/app/assets/javascripts/admin
Krzysztof Kotlarek b120728999
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 16:19:01 +11:00
..
adapters FEATURE: Overhaul of admin API key system (#8284) 2019-11-05 14:10:23 +00:00
components FEATURE: Ability to add components to all themes (#8404) 2019-11-28 16:19:01 +11:00
controllers FEATURE: Ability to add components to all themes (#8404) 2019-11-28 16:19:01 +11:00
helpers DEV: Import set, setProperties, helper, and string functions (#8297) 2019-11-05 12:43:49 -06:00
mixins FEATURE: Ability to add components to all themes (#8404) 2019-11-28 16:19:01 +11:00
models FEATURE: Ability to add components to all themes (#8404) 2019-11-28 16:19:01 +11:00
routes Fix Prettier using correct version (1.19.1) 2019-11-15 10:34:26 -05:00
services DEV: Import Promise from rsvp (#8296) 2019-11-05 10:37:32 -06:00
templates FEATURE: Ability to add components to all themes (#8404) 2019-11-28 16:19:01 +11:00