SchedulerModuleController
FinalYes
Scheduler backend module.
This class is a specific Backend controller implementation and is not considered part of the Public TYPO3 API.
Attributes
- #[AsController]
Table of Contents
Methods
- __construct() : mixed
- getCurrentAction() : SchedulerManagementAction
- This is (unfortunately) used by additional field providers to distinct between "create new task" and "edit task".
- handleRequest() : ResponseInterface
- Entry dispatcher method.
Methods
__construct()
public
__construct(Scheduler $scheduler, TaskSerializer $taskSerializer, SchedulerTaskRepository $taskRepository, IconFactory $iconFactory, UriBuilder $uriBuilder, ModuleTemplateFactory $moduleTemplateFactory, Context $context, TaskService $taskService) : mixed
Parameters
- $scheduler : Scheduler
- $taskSerializer : TaskSerializer
- $taskRepository : SchedulerTaskRepository
- $iconFactory : IconFactory
- $uriBuilder : UriBuilder
- $moduleTemplateFactory : ModuleTemplateFactory
- $context : Context
- $taskService : TaskService
getCurrentAction()
This is (unfortunately) used by additional field providers to distinct between "create new task" and "edit task".
public
getCurrentAction() : SchedulerManagementAction
Return values
SchedulerManagementActionhandleRequest()
Entry dispatcher method.
public
handleRequest(ServerRequestInterface $request) : ResponseInterface
There are two arguments involved regarding main module routing:
- 'action': add, edit, delete, toggleHidden, ...
- 'CMD': "save", "close", "new" when adding / editing a task. A better naming would be "nextAction", but the split button ModuleTemplate and DocumentSaveActions.ts can not cope with a renaming here and need "CMD".
Parameters
- $request : ServerRequestInterface