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_controller.rb | ||
| api_controller.rb | ||
| backups_controller.rb | ||
| badges_controller.rb | ||
| color_schemes_controller.rb | ||
| dashboard_controller.rb | ||
| email_controller.rb | ||
| email_styles_controller.rb | ||
| email_templates_controller.rb | ||
| embeddable_hosts_controller.rb | ||
| embedding_controller.rb | ||
| emojis_controller.rb | ||
| groups_controller.rb | ||
| impersonate_controller.rb | ||
| permalinks_controller.rb | ||
| plugins_controller.rb | ||
| reports_controller.rb | ||
| robots_txt_controller.rb | ||
| screened_emails_controller.rb | ||
| screened_ip_addresses_controller.rb | ||
| screened_urls_controller.rb | ||
| search_logs_controller.rb | ||
| site_settings_controller.rb | ||
| site_texts_controller.rb | ||
| staff_action_logs_controller.rb | ||
| themes_controller.rb | ||
| user_fields_controller.rb | ||
| users_controller.rb | ||
| versions_controller.rb | ||
| watched_words_controller.rb | ||
| web_hooks_controller.rb | ||