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
..
penalty-controller.js.es6	DEV: Import Promise from rsvp (#8296)	2019-11-05 10:37:32 -06:00
period-computation.js.es6	DEV: Move computed to discourseComputed (#8312)	2019-11-07 15:38:28 -06:00
setting-component.js.es6	FEATURE: Ability to add components to all themes (#8404)	2019-11-28 16:19:01 +11:00
setting-object.js.es6	DEV: Move computed to discourseComputed (#8312)	2019-11-07 15:38:28 -06:00