From 67b6997306ccc83f66f8f30d62b59aed2e6e7aff Mon Sep 17 00:00:00 2001 From: Isaac Janzen <50783505+janzenisaac@users.noreply.github.com> Date: Wed, 16 Oct 2024 10:46:15 -0500 Subject: [PATCH] DEV: Add `SearchMenu::Results::Assistant` plugin outlets MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add plugin outlets for each assistant result type - User, Tag and Categories, Groups, etc. This gives us the ability to add content for each _type_ of search suggestion: Screenshot 2024-10-16 at 10 01 09 AM I would have preferred to add a single plugin outlet at the top of the template and pass `this.suggestionType` and `@results`, but that would then require that we carry over a ton of core logic to plugins to calculate which _type_ is being rendered, and it would get unnecessarily messy quick. So instead I opted to create a plugin outlet for each _type_. --- .../app/components/search-menu/results/assistant.hbs | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/app/assets/javascripts/discourse/app/components/search-menu/results/assistant.hbs b/app/assets/javascripts/discourse/app/components/search-menu/results/assistant.hbs index 00a8da03f60..47cd27aa4fb 100644 --- a/app/assets/javascripts/discourse/app/components/search-menu/results/assistant.hbs +++ b/app/assets/javascripts/discourse/app/components/search-menu/results/assistant.hbs @@ -1,6 +1,7 @@