Breaking changes for Optimizely Search & Navigation 12
Known issues and breaking changes for Optimizely Search & Navigation 12, in relation to the previous version (11+), and the steps needed to update affected code.
List of changes
-
EPiServer.Find.TypeSearchExtensions.NestedConventionsRemoved public static members from
EPiServer.Find.TypeSearchExtensions.NestedConventions. They leaked settings between instances of-
EPiServer.Find.IClient -
EPiServer.Find.ClientConventions.NestedConventions.MarkAsNested -
EPiServer.Find.ClientConventions.NestedConventions.Contains(..) -
EPiServer.Find.Helpers.Linq.ExpressionExtensions.GetNestedFieldPath(..)Replace these obsolete references with
client.Conventions.NestedConventions.Contains(..)orclient.Conventions.FieldNameConventions.GetNestedFieldPath(..).
-
-
NestedFacetExtensions
MovedNestedFacetExtensionsfromEPiServer.Find.Api.Facets.NestedFacetExtensionstoEPiServer.Find.NestedFacetExtensions. The class is not part of the core API. It was moved to the namespace of other client extensions. So, you no longer need to add ausingstatement when inserting it. -
EPiServer.Find.ClientConventions.NestedConventionItemWrapperSeparated
EPiServer.Find.ClientConventions.NestedConventionItemWrapperintoEPiServer.Find.ClientConventions.NestedConventionItemInstanceWrapperandEPiServer.Find.ClientConventions.NestedConventionItemTypeWrapper. This was done to handle differences between usingForType(..)andForInstancesOf(..)conventions correctly. -
EPiServer.Find.NestedFacetExtensionsMoved nested facet extensions into
EPiServer.Find.NestedFacetExtensions. This change applies to:EPiServer.Find.TypeSearchExtensions.TermsFacetFor(..) EPiServer.Find.TypeSearchExtensions.DateHistogramFacetFor(..)
Updated 7 days ago