mirror of
https://github.com/discourse/discourse.git
synced 2026-08-09 21:45:25 +08:00
2eb203bb4a`register_admin_dashboard_section` now accepts an optional `settings:` map of setting key to a class exposing `.permit`/`.validate`, so a plugin section can save its own filter selections through the same `PUT /admin/dashboard/sections/:id/settings/:key` mechanism core sections already use, instead of that mechanism being core-only. discourse-solved's "Support" section now uses this: its category filter is genuinely multi-select (like Who's posting/Activity by category) and persists per-site, including converting the `accepted_solutions` report's category filter from a single id to a list. |
||
|---|---|---|
| .. | ||
| accepted_answer_cache.rb | ||
| accepted_answers_helper.rb | ||
| admin_dashboard_support.rb | ||
| admin_dashboard_support_categories_setting.rb | ||
| category_extension.rb | ||
| engine.rb | ||
| first_accepted_post_solution_validator.rb | ||
| guardian_extensions.rb | ||
| post_mover_extension.rb | ||
| post_serializer_extension.rb | ||
| queries.rb | ||
| register_filters.rb | ||
| schema_utils.rb | ||
| seed_admin_dashboard_reports.rb | ||
| topic_extension.rb | ||
| topic_posters_summary_extension.rb | ||
| topic_view_serializer_extension.rb | ||
| user_extension.rb | ||
| user_summary_extension.rb | ||
| web_hook_extension.rb | ||
