GravityKit\GravityMigrate\Migration\ExportRequest

Turns "these forms, this data, this date range" into the payload the export engine takes.

The engine is driven by an options-shaped payload (gk_migrate_export_forms and friends). Each rule here covers a way an export succeeds while carrying the wrong thing: a data type the site has no table for exports nothing, uploads without entries package files nothing refers to, and a reversed date range exports zero rows.

Since: %ver%

Source: src/Migration/ExportRequest.php:25

Details

• Kind: class
• Namespace: GravityKit\GravityMigrate\Migration

Methods

Method	Description
resolve()	The engine payload for one export, or the refusal that stops it.

Method Reference

resolve()

public static function resolve( array $input, Export $export )

The engine payload for one export, or the refusal that stops it.

Parameters

Name	Type	Default	Description
$input	array		Export request: forms (Gravity Forms ids), all_forms (every form instead of named ids), data (data types to carry), date_start and date_end (Y-m-d bounds on entries), include_files (package the referenced uploads inside the bundle).
$export	Export		The export engine, for the data types this site can actually produce.

Returns

• array{payload:array, — forms:array, data:array, dropped:array}|WP_Error

Since: %ver%

Source: src/Migration/ExportRequest.php:82