Do not implement feature with custom code, but use existing feature to
create search_abstract field.
Also execute DataProcessing in AbstractIndexer, not in TcaTableService,
to affect all current available indexers, not only some.
Also this is the place to be.
Respect the following situations during indexing:
- Page is not reachable due to broken root line.
- Page is not reachable due to being below a recycler.
Add functional test to test facet configuration including:
- Mapping (indexing)
- Searching (retrieving of facets)
- Filter (already existed, now based on facet case sensitive)
* To support further configuration, specific to identifiers / tables.
* E.g. mapping and boost configuration should be possible.
* Adjust docs and settings.
* Adjust tests and code.
* Adjust fixtures to be strict mode compatible.
* Adjust documentation to cover requirements for development.
* Notice that strict mode is not supported by TYPO3.
* Document how to handle tests against multiple TYPO3 versions.
* Add typoscript option which TYPO3 tables should be processed and which
should not be processed.
* Respect new optiion in hook.
* Also add necessary tests.
* Remove old no longer needed tests for hook.
* Allow configuration through TypoScript to exclude records for indexing
based on their root line position. Page uids can be configured for
exclusion and all records beneath will be excluded while indexing.
* TCAIndexer is now able to resolve relations of any kind by using TYPO3
Core API.
* Indexed will be a single string or an array, depending of how many
relations were resolved.
* The same value will be indexed as shown by TCA in backend while
editing or displaying.
* FEATURE: Added tests for hook and implemented logic
* To enable updating search index on modifications through TYPO3 API.
* BUGFIX: Fix path for unit test coverage report
* To fix failing delivery to scrutinizer.