Update naming pattern for custom index definitions #33
Comments
kwin
added a commit
that referenced
this issue
Dec 10, 2024
Adobe updated the policy in https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/indexing#preparing-the-new-index-definition Add unit tests This closes #33
kwin
added a commit
that referenced
this issue
Dec 10, 2024
Adobe updated the policy in https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/indexing#preparing-the-new-index-definition Add unit tests This closes #33
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
According to https://experienceleague.adobe.com/en/docs/experience-manager-learn/foundation/development/understand-indexing-best-practices the naming pattern is either
<OOTBIndexName>-<productVersion>-custom-<customVersion>(for customizing OOTB indices) or<prefix>.<customIndexName>-<version>-custom-<customVersion>(for custom indices)The text was updated successfully, but these errors were encountered: