From 2985eadb24870ad33bacbd55fbbe7346ab3f6563 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 29 Sep 2025 13:23:36 +0200 Subject: [PATCH 1/3] Added ComposeAfter to composer used in Examine samples --- 16/umbraco-cms/reference/searching/examine/indexing.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/16/umbraco-cms/reference/searching/examine/indexing.md b/16/umbraco-cms/reference/searching/examine/indexing.md index 0a5983d2804..4b0861b7c0d 100644 --- a/16/umbraco-cms/reference/searching/examine/indexing.md +++ b/16/umbraco-cms/reference/searching/examine/indexing.md @@ -54,6 +54,7 @@ using Umbraco.Cms.Core.DependencyInjection; namespace Umbraco.Docs.Samples.Web.CustomIndexing; +[ComposeAfter(typeof(Umbraco.Cms.Infrastructure.Examine.AddExamineComposer))] public class ExamineComposer : IComposer { public void Compose(IUmbracoBuilder builder) @@ -63,6 +64,8 @@ public class ExamineComposer : IComposer } ``` +Note the use of the `ComposeAfter` attribute. By adding this we guarantee that the composer will run after the core composer responsible for setting up the default index details. + ### Changing field value types By default, Examine will store values into the Lucene index as "Full Text" fields, meaning the values will be indexed and analyzed for a textual search. However, if a field value is numerical, date/time, or another non-textual value type, you might want to change how the value is stored in the index. This will let you take advantage of some value type-specific search features such as numerical or date range. From 571338ebb9451bfa572d23cccc4708062374aa26 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 29 Sep 2025 13:25:55 +0200 Subject: [PATCH 2/3] Removed use of 'we' --- 16/umbraco-cms/reference/searching/examine/indexing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-cms/reference/searching/examine/indexing.md b/16/umbraco-cms/reference/searching/examine/indexing.md index 4b0861b7c0d..644bba29a46 100644 --- a/16/umbraco-cms/reference/searching/examine/indexing.md +++ b/16/umbraco-cms/reference/searching/examine/indexing.md @@ -64,7 +64,7 @@ public class ExamineComposer : IComposer } ``` -Note the use of the `ComposeAfter` attribute. By adding this we guarantee that the composer will run after the core composer responsible for setting up the default index details. +Note the use of the `ComposeAfter` attribute. Adding this guarantees that the composer will run after the core composer responsible for setting up the default index details. ### Changing field value types From e9c9ac2ebe4ba7eaa062bdb7fcac794e303684a2 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 29 Sep 2025 14:06:42 +0200 Subject: [PATCH 3/3] Update 16/umbraco-cms/reference/searching/examine/indexing.md Co-authored-by: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> --- 16/umbraco-cms/reference/searching/examine/indexing.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/16/umbraco-cms/reference/searching/examine/indexing.md b/16/umbraco-cms/reference/searching/examine/indexing.md index 644bba29a46..13c6f5c7095 100644 --- a/16/umbraco-cms/reference/searching/examine/indexing.md +++ b/16/umbraco-cms/reference/searching/examine/indexing.md @@ -64,7 +64,9 @@ public class ExamineComposer : IComposer } ``` -Note the use of the `ComposeAfter` attribute. Adding this guarantees that the composer will run after the core composer responsible for setting up the default index details. +{% hint style="info" %} +The use of the `ComposeAfter` attribute guarantees that the composer will run after the core composer responsible for setting up the default index details. +{% endhint %} ### Changing field value types