Merge pull request #7448 from umbraco/cms/examine-index-example

eshanrnh · web-flow · commit 22c4d36a9486 · 2025-09-29T14:33:19.000+02:00
Added `ComposeAfter` attribute to composer used in Examine sample
diff --git 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,10 @@ public class ExamineComposer : IComposer
 }
 ```
 
+{% 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
 
 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.

Original file line number	Diff line number	Diff line change
`@@ -54,6 +54,7 @@ using Umbraco.Cms.Core.DependencyInjection;`
`54`	`54`
`55`	`55`	`namespace Umbraco.Docs.Samples.Web.CustomIndexing;`
`56`	`56`
	`57`	`+[ComposeAfter(typeof(Umbraco.Cms.Infrastructure.Examine.AddExamineComposer))]`
`57`	`58`	`public class ExamineComposer : IComposer`
`58`	`59`	`{`
`59`	`60`	`public void Compose(IUmbracoBuilder builder)`
`@@ -63,6 +64,10 @@ public class ExamineComposer : IComposer`
`63`	`64`	`}`
`64`	`65`	```
`65`	`66`
	`67`	`+{% hint style="info" %}`
	`68`	+The use of the `ComposeAfter` attribute guarantees that the composer will run after the core composer responsible for setting up the default index details.
	`69`	`+{% endhint %}`
	`70`	`+`
`66`	`71`	`### Changing field value types`
`67`	`72`
`68`	`73`	`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.`