[TASK] update naming according to TYPO3.TYPO3CR.Search

Author: mgoldbeck

Classes/Flowpack/ElasticSearch/ContentRepositoryAdaptor/Command/NodeIndexCommandController.php

@@ -14,7 +14,7 @@
 use TYPO3\Flow\Annotations as Flow;
 use TYPO3\Flow\Cli\CommandController;
 use Flowpack\ElasticSearch\ContentRepositoryAdaptor\Mapping\NodeTypeMappingBuilder;
-use TYPO3\TYPO3CR\SearchCommons\Indexer\NodeIndexingManager;
+use TYPO3\TYPO3CR\Search\Indexer\NodeIndexingManager;
 
 /**
  * Provides CLI features for index handling

Classes/Flowpack/ElasticSearch/ContentRepositoryAdaptor/Eel/ElasticSearchQueryBuilder.php

@@ -16,7 +16,7 @@
 use TYPO3\Eel\ProtectedContextAwareInterface;
 use TYPO3\Flow\Annotations as Flow;
 use TYPO3\TYPO3CR\Domain\Model\NodeInterface;
-use TYPO3\TYPO3CR\SearchCommons\Search\QueryBuilderInterface;
+use TYPO3\TYPO3CR\Search\Search\QueryBuilderInterface;
 
 /**
  * Query Builder for ElasticSearch Queries

Classes/Flowpack/ElasticSearch/ContentRepositoryAdaptor/ElasticSearchClient.php

@@ -47,7 +47,7 @@ class ElasticSearchClient extends \Flowpack\ElasticSearch\Domain\Model\Client {
 	 */
 	public function initializeObject($cause) {
 		if ($cause === \TYPO3\Flow\Object\ObjectManagerInterface::INITIALIZATIONCAUSE_CREATED) {
-			$settings = $this->configurationManager->getConfiguration(\TYPO3\Flow\Configuration\ConfigurationManager::CONFIGURATION_TYPE_SETTINGS, 'TYPO3.TYPO3CR.SearchCommons');
+			$settings = $this->configurationManager->getConfiguration(\TYPO3\Flow\Configuration\ConfigurationManager::CONFIGURATION_TYPE_SETTINGS, 'TYPO3.TYPO3CR.Search');
 			$this->indexName = $settings['elasticSearch']['indexName'];
 		}
 	}

Classes/Flowpack/ElasticSearch/ContentRepositoryAdaptor/Indexer/NodeIndexer.php

@@ -19,7 +19,7 @@
 use TYPO3\Flow\Annotations as Flow;
 use TYPO3\TYPO3CR\Domain\Model\Node;
 use TYPO3\TYPO3CR\Domain\Service\NodeTypeManager;
-use TYPO3\TYPO3CR\SearchCommons\Indexer\AbstractNodeIndexer;
+use TYPO3\TYPO3CR\Search\Indexer\AbstractNodeIndexer;
 
 /*
  * Yes, dirty as hell. But the function is just too helpful...

Classes/Flowpack/ElasticSearch/ContentRepositoryAdaptor/Mapping/NodeTypeMappingBuilder.php

@@ -57,7 +57,7 @@ class NodeTypeMappingBuilder {
 	 */
 	public function initializeObject($cause) {
 		if ($cause === \TYPO3\Flow\Object\ObjectManagerInterface::INITIALIZATIONCAUSE_CREATED) {
-			$settings = $this->configurationManager->getConfiguration(\TYPO3\Flow\Configuration\ConfigurationManager::CONFIGURATION_TYPE_SETTINGS, 'TYPO3.TYPO3CR.SearchCommons');
+			$settings = $this->configurationManager->getConfiguration(\TYPO3\Flow\Configuration\ConfigurationManager::CONFIGURATION_TYPE_SETTINGS, 'TYPO3.TYPO3CR.Search');
 			$this->defaultConfigurationPerType = $settings['defaultConfigurationPerType'];
 		}
 	}

Configuration/Objects.yaml

@@ -14,7 +14,7 @@ Flowpack\ElasticSearch\ContentRepositoryAdaptor\Command\NodeIndexCommandControll
               fileBackend: 'TYPO3\Flow\Log\Backend\FileBackend'
               ansiConsoleBackend: 'TYPO3\Flow\Log\Backend\AnsiConsoleBackend'
           4:
-            setting: TYPO3.TYPO3CR.SearchCommons.elasticSearch.log.backendOptions
+            setting: TYPO3.TYPO3CR.Search.elasticSearch.log.backendOptions
 
 Flowpack\ElasticSearch\ContentRepositoryAdaptor\LoggerInterface:
   scope: singleton

Configuration/Settings.yaml

@@ -1,6 +1,6 @@
 TYPO3:
   TYPO3CR:
-    SearchCommons:
+    Search:
 
       elasticSearch:
 

README.md

@@ -11,7 +11,7 @@ main functionalities:
 
 Relevant Packages:
 
-* `TYPO3.TYPO3CR.SearchCommons`: provides common functionality for searching TYPO3CR nodes,
+* `TYPO3.TYPO3CR.Search`: provides common functionality for searching TYPO3CR nodes,
   does not contain a search backend
 
 * `Flowpack.ElasticSearch.ContentRepositoryAdaptor`: this package
@@ -25,15 +25,15 @@ Relevant Packages:
 ## Version 2 vs Version 1
 
 * Version 1 is the initial, productive version of the Neos ElasticSearch adapter.
-* Version 2 has a dependency on TYPO3.TYPO3CR.SearchCommons; which contains base functionality
+* Version 2 has a dependency on TYPO3.TYPO3CR.Search; which contains base functionality
   which is also relevant for other search implementations (like the SQLite based SimpleSearch).
 
 The configuration from Version 1 to Version 2 has changed; here's what to change:
 
 **Settings.yaml**
 
 1. Change the base namespace for configuration from `Flowpack.ElasticSearch.ContentRepositoryAdaptor`
-   to `TYPO3.TYPO3CR.SearchCommons`. All further adjustments are made underneath this namespace:
+   to `TYPO3.TYPO3CR.Search`. All further adjustments are made underneath this namespace:
 
 2. (If it exists in your configuration:) Move `indexName` to `elasticSearch.indexName`
 
@@ -179,7 +179,7 @@ of `__typeAndSupertypes` containing `TYPO3.Neos:Document`.
 **Normally, this does not need to be touched, as this package supports all TYPO3 Neos data types natively.**
 
 Indexing of properties is configured at two places. The defaults per-data-type are configured
-inside `TYPO3.TYPO3CR.SearchCommons.defaultConfigurationPerType` of `Settings.yaml`.
+inside `TYPO3.TYPO3CR.Search.defaultConfigurationPerType` of `Settings.yaml`.
 Furthermore, this can be overridden using the `properties.[....].search` path inside
 `NodeTypes.yaml`.
 
@@ -194,7 +194,7 @@ Example (from the default configuration):
  # Settings.yaml
 TYPO3:
   TYPO3CR:
-    SearchCommons:
+    Search:
       defaultConfigurationPerType:
 
         # strings should, by default, not be included in the _all field; and