v2.0.3 for Elastic Search

Fixes #104

v4.1.6

Additional fixes for: Range queries are not added to the $filter expression #87

6.0.1 for Azure Search

Fixes: Long Range queries are not working correctly #101

v6.0.0 for Azure Search

New major version targeting Umbraco 13, .NET 8 and support Umbraco's Content Delivery API.

Breaking Changes

• Breaking Change: Bootstrap ExamineX with IUmbracoBuilder extension methods instead of using IComposer #99
  • ExamineX now requires an explicit call to be enabled. You'll need to enable the integration in your Startup.cs and add the .AddExamineXAzureSearch() call after the .AddComposers() call. This

    public void ConfigureServices(IServiceCollection services)
    {
        services.AddUmbraco(_env, _config)
            .AddBackOffice()
            .AddWebsite()
            .AddDeliveryApi()
            .AddComposers()
            .AddExamineXAzureSearch()
            // If you are using the BlobMedia ExamineX feature
            //.AddExamineXForBlobMedia()
            // If you are using the Forms ExamineX feature
            //.AddExamineXForUmbracoForms()
            .Build();
    }

• Breaking Change: Set filterable to 'false' on custom field definition of type 'Edm.String' #95

Possible Breaking Change

Examine and ExamineX do not expect that you will pin a reference to the ISearcher which is resolved from the IIndex.Searcher property. The IIndex.Searcher property is not a singleton and cannot and should not be pinned into a static or singleton field in your code. Always reference the searcher via the property IIndex.Searcher. This is especially true with ExamineX 6.0.0.

Fixes

• Fix: FieldDefinitionTypes.DateTime field not being mapped to SearchFieldDataType.DateTimeOffset #98

v5.2.0 for Azure Search

Possible Breaking Change

Examine and ExamineX do not expect that you will pin a reference to the ISearcher which is resolved from the IIndex.Searcher property. The IIndex.Searcher property is not a singleton and cannot and should not be pinned into a static or singleton field in your code. Always reference the searcher via the property IIndex.Searcher. This is especially true with ExamineX 5.2.0.

Fixes

• Fix: FieldDefinitionTypes.DateTime field not being mapped to SearchFieldDataType.DateTimeOffset #98

Changes

• ExamineX Nuget packages now split into additional references as transient dependencies (this will be transparent to the end user)

v5.1.0

New features:

• Support for Umbraco Forms indexes. This is typically not a requirement and is fairly uncommon when using Umbraco Forms. If you rely on Umbraco Forms indexes - which are generally used to render form entries on the front-end - then you can now use the ExamineX.AzureSearch.Umbraco.Forms package supporting Umbraco Forms 12.1.2+

Bug fixes:

• #92
• #89
• #87

v5.0.1

Fixes: Range queries are not added to the $filter expression #87

v5.0.0

New major version targeting Umbraco 12 and .NET 7 with all dependencies updated to latest versions.

v4.2.0 for Azure Search

Possible Breaking Change

Examine and ExamineX do not expect that you will pin a reference to the ISearcher which is resolved from the IIndex.Searcher property. The IIndex.Searcher property is not a singleton and cannot and should not be pinned into a static or singleton field in your code. Always reference the searcher via the property IIndex.Searcher. This is especially true with ExamineX 4.2.0.

Fixes

• Fix: FieldDefinitionTypes.DateTime field not being mapped to SearchFieldDataType.DateTimeOffset #98

Changes

• ExamineX Nuget packages now split into additional references as transient dependencies (this will be transparent to the end user)

v4.1.9

• Fixes: If the index doesn't exist but a search is executed a null reference exception may occur #96
• Enhancment: Allow customization of the internal SearchClientOptions used to create the SearchIndexClient #97