By nicxvan on
Change record status:
Draft (View all draft change records)
Project:
Issue links:
Description:
The batch api is complex, there is a new BatchProcessor services that serves as a simple wrapper of the current batch api.
Map of functions to methods:
| Before | After |
|---|---|
batch_set |
Drupal::service(BatchProcessor::class)->queue() |
batch_get |
Drupal::service(BatchProcessor::class)->getCurrentBatch() |
batch_process |
Drupal::service(BatchProcessor::class)->process() |
_batch_append_set |
Drupal::service(BatchProcessor::class)->appendSet() |
_batch_populate_queue |
Drupal::service(BatchProcessor::class)->queuePopulate() |
_batch_queue |
Drupal::service(BatchProcessor::class)->getQueue() |
_batch_process |
Drupal::service(BatchProcessor::class)->processQueue() |
_batch_current_set |
Drupal::service(BatchProcessor::class)->getCurrentSet() |
_batch_next_set |
Drupal::service(BatchProcessor::class)->nextSet() |
_batch_finished |
Drupal::service(BatchProcessor::class)->finishedProcessing() |
_batch_shutdown |
Drupal::service(BatchProcessor::class)->shutdown() |
_batch_needs_update |
Drupal::service(BatchProcessor::class)->needsUpdate() |
Impacts:
Module developers
