Skip to content

Conversation

@cirk2
Copy link

@cirk2 cirk2 commented Oct 28, 2020

What this pr does

Typo3 7.4 Introduced Data Processing for the FLUIDTEMPLATE cObject. I have found it to be quite useful but it is not globally available in extensions.
This PR Enables the feature on the Results Action and should be easy to be expanded to the other actions in the SearchController.
Location of the dataProcessing block in the setup is just my first idea, and retrieval of the value probably should be packed into a getter.

How to test

Configuration/TypoScript/Examples/DataProcessing/setup.txt has an example for TypoScript setup. A DataProcessor has to be Provided for testing, either one of the ones Supplied by Typo3 or a custom one.

Copy link
Collaborator

@dkd-kaehm dkd-kaehm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please explain some exact use case for this stuff?


public function __construct()
{
$this->contentDataProcessor = GeneralUtility::makeInstance(ContentDataProcessor::class);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use Injector style, to be able to mock this stuff in tests.

'arguments' => $arguments
];

$values = $this->emitActionSignal(__CLASS__, __FUNCTION__, [$values]);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this signal unusable for the things you want?
If there is not all what you want, pack this in array.
Would propose to extend all the signals and pack the stuff in the docs and examples.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Main difference is that Data Processing is configured via typoscript, allowing to plug different configs in places.
Instead of Signals which are global.

Copy link
Collaborator

@dkd-kaehm dkd-kaehm Oct 29, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, i mean that we could plug this stuff via this signal[s], via something like "Facade/Gateway" or some other design pattern.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ContentDataProcessor only needs the ContentObjectRenderer which we can get pretty much anywhere injection works. And the configuration from Typoscript of course.
So yeah we could plug it via the signals.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cirk2 cirk2 force-pushed the feature/DataProcessing branch from c443899 to 88bf0d5 Compare October 29, 2020 10:04
@dkd-kaehm dkd-kaehm force-pushed the release-11.5.x branch 2 times, most recently from caabbba to e4519e9 Compare July 30, 2024 06:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants